-Karthik--
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/-/uehied9ntTsJ.
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.
Interesting question. AFAIK no one has come up with an OpenID 2.0 extension for receiving an OAuth 2 access token. But I don't see anything wrong with doing that. Ultimately this scenario will be covered by OpenID Connect though, which is probably why the extension case isn't getting any mindshare.
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre
On Mon, Jul 23, 2012 at 8:42 PM, Karthik Nagaraju wrote:
Hi,We have an identity provider application which is currently supporting open id 2.0 with oauth 1.0 extension support using DNOA3.4. We are validating the move to oAuth 2.0.Is there oauth2.0 extension support available with DNOA4.1?Has any one tried oauth2.0 in conjunction with openid 2.0?What is the recommended approach for supporting OpenId with oAuth2.0 using DNOA?I would appreciate any pointers towards the same.
-Karthik--
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/-/uehied9ntTsJ.
To post to this group, send email to dotnet...@googlegroups.com.
To unsubscribe from this group, send email to dotnetopenid+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/z3ezervlKUMJ.
To unsubscribe from this group, send email to dotnetopenid...@googlegroups.com.