> -Original Message-
> From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Rifaat Shekh-
> Yusef
> Sent: Friday, January 05, 2018 12:30 PM
> To: e...@rtfm.com
> Cc: oauth@ietf.org; iesg-secret...@ietf.org; oauth-cha...@ietf.org
> Subject: [EXTERNAL] [OAUTH-WG] Publication has been requ
From: William Denniss [mailto:wdenn...@google.com]
Sent: Tuesday, January 02, 2018 5:38 PM
To: Hollenbeck, Scott
Cc: oauth@ietf.org
Subject: [EXTERNAL] Re: [OAUTH-WG] OAuth 2.0 Device Flow LC Comment (and OpenID
Connect)
On Mon, Nov 27, 2017 at 6:32 AM Hollenbeck, Scott
mailto:shollenb
On Jan 2, 2018, at 4:08 PM, William Denniss
mailto:wdenn...@google.com>> wrote:
On Fri, Dec 15, 2017 at 11:12 PM, Vladimir Dzhuvinov
mailto:vladi...@connect2id.com>> wrote:
On 15/12/17 00:43, William Denniss wrote:
> On Fri, Dec 8, 2017 at 11:42 AM, Vladimir Dzhuvinov
> mailto:vladi...@connec
I have reviewed draft-ietf-oauth-device-flow-07. Just one comment regarding
Section 5.1:
Would it be possible to suggest some minimally acceptable entropy value? The
text says "The user code SHOULD have enough entropy that when combined with
rate limiting makes a brute-force attack infeasible",
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Bill Burke
Sent: Monday, June 12, 2017 9:23 AM
To: Aaron Parecki
Cc: OAuth WG
Subject: [EXTERNAL] Re: [OAUTH-WG] oauth with command line clients
I've read about these techniques, but, its just not a good user experience.
I'm thinking m
Thanks, Nat.
Scott
From: Nat Sakimura [mailto:sakim...@gmail.com]
Sent: Tuesday, September 27, 2016 10:03 AM
To: Hollenbeck, Scott; Justin Richer; oauth@ietf.org
Subject: Re: [OAUTH-WG] Identity Provider Interop Testing?
There is an interop list which does not have IPR requirement.
The IPR
> -Original Message-
> From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Justin Richer
> Sent: Monday, September 19, 2016 9:35 AM
> To: oauth@ietf.org
> Subject: Re: [OAUTH-WG] Identity Provider Interop Testing?
>
> You're better off contacting the OpenID Connect working group and t
I'm looking to do some OpenID Connect interoperability testing with someone who
has implemented an identity provider. I have a relying party implementation
that's been tested with Microsoft Hotmail and Google Gmail. I'd like to add
support for at least one more IDP. Can anyone help?
Scott
: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hollenbeck,
> Scott
> Sent: Tuesday, January 19, 2016 9:40 AM
> To: 'OAuth@ietf.org'
> Subject: Re: [OAUTH-WG] Cross-Area Review Request for RDAP
> Authentication
>
> > -Original Message-
> > From:
> -Original Message-
> From: Hollenbeck, Scott
> Sent: Monday, January 11, 2016 8:31 AM
> To: OAuth@ietf.org
> Subject: Cross-Area Review Request for RDAP Authentication
>
> I'd like to ask folks who are more familiar with OAuth than I am to
> please re
I'd like to ask folks who are more familiar with OAuth than I am to please
review an I-D I've written that describes an approach to using OpenID Connect
with the Registration Data Access Protocol (RDAP, a product of the WEIRDS WG).
Those of you who are familiar with WHOIS will understand the mot
I was going to ask this question during the just-concluded WG session at
IETF-92, but with a full agenda and little time I thought it might be better to
ask this question on-list.
The Registration Data Access Protocol (RDAP, a work product of the WEIRDS WG)
uses a RESTful web service to access
12 matches
Mail list logo
