Am 16.07.2010 18:35, schrieb Brian Eaton:
On Fri, Jul 16, 2010 at 4:47 AM,<wolfgang.steigerw...@telekom.de> wrote:
+1 to Thorstens statement. There are use cases beyond local deployments.
Definitely.
For example, I'm interested in deployments where neither clients nor
resource servers need secret keys. This makes adding new clients and
resource servers trivial.
The challenge here is that even though lots of people are interested
in various semantics for "scope", and various types of relations
between clients, resource servers, and authorization servers, not
everyone has the same use cases and requirements.
then we should put those use cases and requirements on the table and try
to find a solution fulfilling these different needs. That's what (from
my point of view) standard definition is all about.
What do you think?
regards,
Torsten.
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
