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. 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.
*/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20221013/148583fb/attachment.sig>