We might really want to include a token exchange (or transition) use case where Kerberos service tickets (ST) get involved. As as example, a workload provides a Kerberos ST to an AS using typical approach "Authorization: Negotiate ****" for that. Then, an AS issues an OAuth Bearer (or any other token) if this AS
successfully validates provided Kerberos ST, and
allows this sort of operation for a caller
There are lots of Orgs completely or partially in a Windows shop, and they want their apps to talk to apps that use OAuth and so forth with a minimal set of changes (leveraging and leaving unchanged what MS Windows AD provides to their legacy apps).
There is a need for this use case in the way I see it, despite the fact that Kerberos is a 30 years old protocol.
We might really want to include a token exchange (or transition) use case where Kerberos service tickets (ST) get involved. As as example, a workload provides a Kerberos ST to an AS using typical approach "Authorization: Negotiate ****" for that. Then, an AS issues an OAuth Bearer (or any other token) if this AS
There are lots of Orgs completely or partially in a Windows shop, and they want their apps to talk to apps that use OAuth and so forth with a minimal set of changes (leveraging and leaving unchanged what MS Windows AD provides to their legacy apps).
There is a need for this use case in the way I see it, despite the fact that Kerberos is a 30 years old protocol.