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]>
Newsgroups gmane.ietf.ipp
Message-ID <[email protected]>
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.
*/

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAmNIdCkACgkQqskbKLDW
1N1U1g//dYuESkbVky5bb6ir8iRt3toHq2s8pnh1m3qSy7fX7X7oetZr17ipkQBu
tIHvoCa8jMFqUxaAfYyiuW0pLPW+7+z76K49FYUw0EI+aUIYt/MURQU+eRbehGr3
7sBBjC2d4tA3I9WVC0nm5Eg9XOCm60nCV5Ag83Jy1TjPn9yha7s0aTumM5InxY3z
phThdnmt5O0UR+VG+5kcXeSw2jczpx6+wjkIX0+wNGO2KvnzwVOlTMdjX+/Xhbwt
22vJblblDoPC/bBRKSPVltBqnjIHd+6AxGWdGLTGGf42eKO3PxrldDWtHZj9fzBv
Jx4S1o/T1ocijiO9TCIRqOiUM/6WsU/aDoQ10PE+RiuW5qAfbln9RmxB0SmTxFV2
4NoT198NThMAoAVadp+58SxcuAluOv3wfvf73yDmdUijzKxsJycBptUjPHZ2LhUk
XD9I63RM+NFA6n5JfIcAD6lMh/eGewBV7TfUO+djiQdK9/sRH/aB//p5RtVMh5ce
3coC0h/xQFdT/ZAI2GCQX8pUi5kToQgQjfGn6iii46MokYU/xFdmEyycfKu7j4FP
D7PsvOOIJKy9/RvAZPrj2QkWy9o8k6IDDxYbdtBR0+W0pIfUSWHdr/VAS1/psmxR
5R5J4YwKEjHUQa7tL6FNbdOCKyTdNb7jO6s4IxtIruJv1QJTKI8=
=XHbr
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.