> On 20 Feb 2024, at 06:44, Sachin Mamoru wrote:
>
>
> Hi All,
>
> When we request an access token using 3 scopes (scope1, scope2, scope3).
> Then will receive a refresh token (refresh_token1) with the access token.
>
> After that will request another access token with refresh_token1 and
Hi All,
When we request an access token using 3 scopes (scope1, scope2, scope3).
Then will receive a refresh token (refresh_token1) with the access token.
After that will request another access token with refresh_token1 and
provide the scope list as scope1 and scope2 (Narrow down scopes).
Hi All,
When we request an access token using 3 scopes (scope1, scope2, scope3).
Then will receive a refresh token (refresh_token1) with the access token.
After that will request another access token with refresh_token1 and
provide the scope list as scope1 and scope2 (Narrow down scopes).
Not sure what I'm supposed to send please be detailed in the instructions
please unblock my stake.us account though I can no longer log in using sign
in through my Google
On Thu, Feb 15, 2024, 3:01 PM wrote:
> Send OAuth mailing list submissions to
> oauth@ietf.org
>
> To subscribe or
Inline:
On Mon, Feb 19, 2024, 7:34 PM wrote:
> Orie, thanks for the response
>
>
>
> I’m still confused on this charter proposal as I read this charter it is
> to create architecture, patterns and definitions for electronic
> credentials. The charter should be free of any technology including
Orie, thanks for the response
I’m still confused on this charter proposal as I read this charter it is to
create architecture, patterns and definitions for electronic credentials. The
charter should be free of any technology including W3C, if people want clarity
about what an electronic
See the following PR related to registrations of media types that rely on
multiple structured suffixes, for example:
application/foo+bar+cose would require `+bar+cose` , `+cose`
application/foo+bar+jwt would require `+bar+jwt`, `+bar+jwt`
application/foo+bar+sd-jwt would require `+bar+sd-jwt`,
Internet-Draft draft-ietf-oauth-identity-chaining-01.txt is now available. It
is a work item of the Web Authorization Protocol (OAUTH) WG of the IETF.
Title: OAuth Identity and Authorization Chaining Across Domains
Authors: Arndt Schwenkschuster
Pieter Kasselmann
Hi Aaron,
(To be honest, I haven’t expected to receive feedback for my inquiry after that
long timespan. I thought my question was lost due to IETF going on at the time.)
Thanks for taking the time to answer. The draft you mentioned looks
interesting, although I don’t think it fits our
