Hi,
In the last days, I dealed with the Open ID Connect Basic Spec and google's implementation of OAuth 2, which contains some extensions, that go hand in hand with Open Id connect to Authenticate users.
So let's say my client got an access_token from google using OAuth 2 and Open Id Connect and let's also assume, I have validated this token regarding thinks like audience and issuer.
Would it be a good idea to pass this token to a rest-service, to show, that the client is acting on behalf of the authenticated user?
If yes, the server would have to check, if the audience is a trusted client an so on, wouldn't it?
If this isn't a good idea, how to show the service that the client acts upon this user?
On possibility were to write an auth-server that exchanges this token for another, which can be used to access the service.
What do you think about this solution? Are there other/ better solutions for this?
Thanks for your help.
Wishes,
Manfrd
--
You received this message because you are subscribed to the Google Groups "DotNetOpenAuth" group.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/QLWFlMfJj3AJ.
To post to this group, send email to dotnet...@googlegroups.com.
To unsubscribe from this group, send email to dotnetopenid...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dotnetopenid?hl=en.