Re: [OAUTH-WG] Detecting revoked token in OAuth 2.0 client libraries

2012-01-09 Thread Andreas Åkre Solberg
Den 9. jan.2012 kl. 17:35 skrev Torsten Lodderstedt: > Hi, > > an invalid token should cause the server to reply with status code 401. Thanks for the tip, both of you. Andreas___ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinf

Re: [OAUTH-WG] Detecting revoked token in OAuth 2.0 client libraries

2012-01-09 Thread Torsten Lodderstedt
Åkre Solberg Verzonden: maandag 9 januari 2012 9:41 Aan: oauth@ietf.org Onderwerp: [OAUTH-WG] Detecting revoked token in OAuth 2.0 client libraries Hi, I'm trying to do an OAuth 2.0 library, and got a question: I cannot find a standardized way for an OAuth protected endpoint to report to

Re: [OAUTH-WG] Detecting revoked token in OAuth 2.0 client libraries

2012-01-09 Thread Bart Wiegmans
to determine token invalidity. With kind regards, Bart Wiegmans -Oorspronkelijk bericht- Van: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] Namens Andreas Åkre Solberg Verzonden: maandag 9 januari 2012 9:41 Aan: oauth@ietf.org Onderwerp: [OAUTH-WG] Detecting revoked token in

[OAUTH-WG] Detecting revoked token in OAuth 2.0 client libraries

2012-01-09 Thread Andreas Åkre Solberg
Hi, I'm trying to do an OAuth 2.0 library, and got a question: I cannot find a standardized way for an OAuth protected endpoint to report to the client that the Token is not valid (expired or revoked). As a library developer, I'd like to take away as much of possible of the OAuth logic from th