Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try to implement clientside API for otps that is both backwards compatible and has the ability to be efficient. #45

Closed
wants to merge 2 commits into from

Conversation

abadger
Copy link
Contributor

@abadger abadger commented Jul 3, 2013

This is a pretty big patch and a pretty big change. Take a look and make as many comments as you feel like. I can add more comments, improve the documentation, or whatever you feel is needed.

compatible and has the ability to be efficient.
invalid, the server will return a 403 http response code to indicate an error.
If the API receives a 403 from sending the username and password, it will then
try sending a ``session_id`` if it has given one. If the API receives a 403
from this as well, thenit will translate this into a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing space "thenit"

I'd suggest changing the "translate this into a..." into "will throw"

``session_id`` for the logged in user. If one or both of the pieces are
invalid, the server will return a 403 http response code to indicate an error.
If the API receives a 403 from sending the username and password, it will then
try sending a ``session_id`` if it has given one. If the API receives a 403
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

grammar here is not quite right and I'm not sure how it should be. "if it has given one"... should that be "if it has one"?

@pypingou
Copy link
Member

Looks generally quite nice, looking forward to test it a little on stg :)

@abadger
Copy link
Contributor Author

abadger commented Aug 6, 2014

At flock 2014 we decided to close this. We're starting to think that BaseClient is legacy and that OpenId BaseClient is the wave of the future. So we're going to ignore the question of handling otp in BaseClient and figure out how to add it to OpenIdBaseClient instead.

@abadger abadger closed this Aug 6, 2014
@abadger abadger deleted the feature/otp-support-take-2 branch August 6, 2014 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants