Skip to content
This repository was archived by the owner on Apr 11, 2019. It is now read-only.

Conversation

wvdemeer
Copy link

I have noticed that C-BAS in some cases returns credentials with an expiration date that is missing a timezone. This is a major bug: A client can't know if the returned date is in the UTC timezone, in the server's local timezone, or in some other timezone. It also means that the date is not valid RFC3339 (since that requires a timezone at all time). So RFC3339 date parsers might fail for such dates. The jFed client (and probably others as well) will get into trouble because of missing timezones.
In my opinion, this timezone bug is very bad and need to be fixed...

This pull request tries to fix these issues. However, I'm not sure if everything I've done is 100% correct: I'm not very experienced with python and the handling of dates in python (with naive and aware dates etc) is confusing.
Also note that some of the changes are done in "src/vendor" which means they are changes in external libraries used by C-BAS.

It would be great if you could review (and test) these changes!

@wvdemeer
Copy link
Author

wvdemeer commented Nov 3, 2016

Any news on this? In my opinion, this is about a critical bug...

By the way, I see that the tests fail with
IOError: [Errno 2] No such file or directory: '/home/travis/build/EICT/C-BAS/test/creds/root-cred.xml'
so I guess the tests need to be fixed?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant