> more ready code to start from.
>
> Does this still fit your vision too described this way?
>
> BR Kristoffer
>
> -Original Message-----
> From: Igor Faynberg [mailto:igor.faynb...@alcatel-lucent.com]
> Sent: Monday, February 07, 2011 5:21 PM
> To: Kristof
Hannes,
A comprehensive list!
I am in support of all items listed, and I commit to reviewing all of
them (and contributing where I will see significant gaps).
One comment on the use cases (my pet peeve). Those were specifically
requested by Peter at the first OAuth meeting, and I think they
B) HTTP Authentication: MAC Authentication
http://datatracker.ietf.org/doc/draft-hammer-oauth-v2-mac-token/
In favor of adopting as WG item, willing to review.
C) Token Revocation
http://tools.ietf.org/html/draft-lodderstedt-oauth-revocation-01
In favor of adopting as WG item, willing to rev
t.com]
Sent: Monday, February 07, 2011 5:21 PM
To: Kristoffer Gronowski
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] New Working Group Items?
Kristoffer,
I assume you mean an interface between the authorization server and the
resource server. If so, I believe it definitely merits a serious discu
fit your vision too described this way?
>
> BR Kristoffer
>
> -Original Message-
> From: Igor Faynberg [mailto:igor.faynb...@alcatel-lucent.com]
> Sent: Monday, February 07, 2011 5:21 PM
> To: Kristoffer Gronowski
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG
from.
Does this still fit your vision too described this way?
BR Kristoffer
-Original Message-
From: Igor Faynberg [mailto:igor.faynb...@alcatel-lucent.com]
Sent: Monday, February 07, 2011 5:21 PM
To: Kristoffer Gronowski
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] New Working Group
Kristoffer,
I assume you mean an interface between the authorization server and the
resource server. If so, I believe it definitely merits a serious
discussion, and I support the idea in principle.
On this subject, I think we need even more work defining the token and
linking it to the resou
f.org
Subject: Re: [OAUTH-WG] New Working Group Items?
Hi Kristoffer,
Hannes compiled the list :-)
regards,
Torsten.
Am 07.02.2011 22:10, schrieb Kristoffer Gronowski:
Hi Torsten!
Great that you compiled the list on WG items.
IMO there is one item missing and that is to create an optional f
Hi Kristoffer,
Hannes compiled the list :-)
regards,
Torsten.
Am 07.02.2011 22:10, schrieb Kristoffer Gronowski:
Hi Torsten!
Great that you compiled the list on WG items.
IMO there is one item missing and that is to create an optional formal
interface between the authorization server and the
Hi Torsten!
Great that you compiled the list on WG items.
IMO there is one item missing and that is to create an optional formal
interface between the authorization server and the protected resource.
It could increase the productivity of creating the oauth protected web services
when the auth se
Long introduction - here are the documents:
A) Simple Web Discovery (SWD)
http://www.ietf.org/id/draft-jones-simple-web-discovery-00.txt
I consider authorization server endpoints and capabilities discovery an
important aspect and would be willed to review.
B) HTTP Authentication: MAC Aut
> -Original Message-
> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
> Of Hannes Tschofenig
> Sent: Thursday, February 03, 2011 8:19 AM
> A) Simple Web Discovery (SWD)
> http://www.ietf.org/id/draft-jones-simple-web-discovery-00.txt
This has no business in this
Hannes,
I would like one more item in the list:
* OAuth2 discovery from the response to any HTTP request, probably via a
WWW-Authenticate response header. I am keen to contribute, and perhaps
co-author such a spec.
> B) HTTP Authentication: MAC Authentication
> http://datatracker.ietf.org/doc/
Hi all,
while we are hopefully coming to an end with the main specification (and
the two other WG items) I need to put text for re-chartering together.
The entire process typically takes a little while because
* I need your feedback (hence this mail) of what you guys want to work on
* I have
14 matches
Mail list logo
