Hi Torsten,
I apologize if this is a duplicate response, but I just realized I responded to my greenbutton-dev email address in my initial response and wanted to be sure you got my reply. For the situation under discussion, there is no data at the (2) resource server available for the client to access at the time the resource owner grants them access. Best regards, Don Donald F. Coffin Founder/CTO REMI Networks 22751 El Prado Suite 6216 Rancho Santa Margarita, CA 92688-3836 Phone: (949) 636-8571 Email: <mailto:donald.cof...@reminetworks.com> donald.cof...@reminetworks.com From: Torsten Lodderstedt [mailto:tors...@lodderstedt.net] Sent: Sunday, February 09, 2014 10:29 PM To: Donald Coffin; oauth@ietf.org Cc: greenbutton-dev Subject: AW: [OAUTH-WG] Should data exist for an Oauth access token request to be granted? Hi Donald, do you mean data regarding the particular user do not exist (1) at the authorization server or (2) the resource server? Regards, Torsten. -------- Ursprüngliche Nachricht -------- Von: Donald Coffin Datum:10.02.2014 03:22 (GMT+01:00) An: oauth@ietf.org Cc: greenbutton-dev Betreff: [OAUTH-WG] Should data exist for an Oauth access token request to be granted? We are having a bit of a philosophical discussion regarding the requirement for data to exist as a requirement for an OAuth 2.0 access token to be granted and I’d like to get the opinions of the IETF Oauth WG. The two points of view are: · There are no requirements in “The OAuth 2.0 Framework” [RFC6749] specification that requires data to exist prior to an access token being granted and therefore the requirement that data exist should NOT be a consideration for granting or denying an access token request, as long as all of the other requirements for granting of an access token are met. · There are many potential applications that are a one-shot access request. These would be confused if they receive an access token allowing them to access information that does NOT exist. A potential solution that might meet both requirements is to add a SCOPE parameter the client MAY provide indicating an access token should only be issued if data does exist. The default would be that absent the SCOPE parameter the Authorization Server would issue an approved access token regardless of the existence or absence of data at the time of the request. I’d like to hear what the WG feels is a best practice solution to resolve our existing implementation conflict. Best regards, Don Donald F. Coffin Founder/CTO REMI Networks 22751 El Prado Suite 6216 Rancho Santa Margarita, CA 92688-3836 Phone: (949) 636-8571 Email: donald.cof...@reminetworks.com
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
