> *Sent:* Thursday, April 19, 2012 5:08 PM
> *To:* Lewis Adam-CAL022
> *Cc:* Justin Richer; oauth@ietf.org
>
> *Subject:* Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
>
> ** **
>
> A browser isn't required. The browser based flows are pretty common with
&g
gt;Cc: oauth@ietf.org
>Sent: Thursday, April 19, 2012 3:03 PM
>Subject: Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
>
>
>Using the browser as part of the AS interaction allows you to more easily
>collect the users consent.
>
>
>Once you get the tokens based
ay, April 19, 2012 5:03 PM
> To: Lewis Adam-CAL022; jric...@mitre.org
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
>
> Using the browser as part of the AS interaction allows you to more easily
> collect the users consent.
>
> On
Thursday, April 19, 2012 5:08 PM
To: Lewis Adam-CAL022
Cc: Justin Richer; oauth@ietf.org
Subject: Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
A browser isn't required. The browser based flows are pretty common with OAuth
but they are certainly not the only way to get a token.
The
Adam-CAL022; jric...@mitre.org
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
Using the browser as part of the AS interaction allows you to more easily
collect the users consent.
Once you get the tokens based on that consent, everything is 'RE
an’t my native client make RESTful API calls to the AS and
> RS natively?
>
> ** **
>
> Tx!
>
> adam
>
> ** **
>
> *From:* Justin Richer [mailto:jric...@mitre.org]
> *Sent:* Friday, April 13, 2012 11:38 AM
> *To:* Lewis Adam-CAL022
> *Cc:
Using the browser as part of the AS interaction allows you to more easily
collect the users consent.
Once you get the tokens based on that consent, everything is 'RESTful'
Original message
Subject: Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
From: Lewis Adam-
external or embedded? Why can't my
native client make RESTful API calls to the AS and RS natively?
Tx!
adam
From: Justin Richer [mailto:jric...@mitre.org]
Sent: Friday, April 13, 2012 11:38 AM
To: Lewis Adam-CAL022
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Using OAuth to get a JWT/SAML token
I
Inline.
On 2012-04-13, at 9:13 PM, Lewis Adam-CAL022 wrote:
> Hi Justin …
>
> In your application, to start things off, you fire off a web browser to the
> authorization server's authorization endpoint. The user logs in to the
> authorization server through the web browser, approves this copy
Hi Justin ...
In your application, to start things off, you fire off a web browser to the
authorization server's authorization endpoint. The user logs in to the
authorization server through the web browser, approves this copy of your app,
and gets redirected to "myapp://oauthcallback?code=basdf
If the mobile device has a web browser (such as a smart phone), then
this is pretty easy, and you've got a couple of options.
One of the best options when the token is on behalf of an end user is,
in my opinion, to use the authorization code flow like this: First,
register what's called a "pub
Hi all,
I've been talking to some of you off line about this already, but I need some
help in terms of implementation. I would like to use OAuth as a means to get
either a JWT or SAML token to a client running on a handheld device. This is
something that I'm looking to prototype (as part of a
12 matches
Mail list logo
