Re: IPP OAuth 2.0 question / potential gap: How should the Client manage multiple access tokens or realm identities?

"Kennedy, Smith \(Wireless & IPP Standards\) via ipp" <[email protected]> Thu, 13 Oct 2022 20:37:18 +0000

Newsgroups	gmane.ietf.ipp
Message-ID	<[email protected]>


> On Oct 13, 2022, at 2:25 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected]> wrote:
> 
> Signed PGP part
> CAUTION: External Email
> 
> Hi there,
> 
> I was having another discussion with HP's OAuth 2.0 folks over the last few days, and one of the things they are working on is guidance for the client on how it should or could manage the circumstance where the client device holds access tokens for multiple "realms" (i.e., work printing, home printing). If it was all just local information similar to Wi-Fi "profile" information maintained on the client, that would just be left up to the client's implementation.
> 
> I found this page that seems to talk through some of these concepts.

Here's the link I meant to provide, which discussed it from an OIDC perspective: https://developer.okta.com/docs/guides/oin-oidc-multi-tenancy/main/#tenants-in-okta <https://developer.okta.com/docs/guides/oin-oidc-multi-tenancy/main/#tenants-in-okta>

> I will continue to read, but wanted to share in case others have already developed plans or thoughts in this area, that we could leverage.
> 
> Cheers,
> 
> Smith
> 
> /**
>    Smith Kennedy
>    HP Inc.
> */
> 
> 
>

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp

signature.asc (application/pgp-signature, 833 B)