-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get a kerberos TGT via AAD #45
Comments
This depends on #29 because we can't pass the tgt parameter during the auth using Microsoft's msal. |
It also depends on #35 because only a ConfidentialClient can obtain tgts. |
Perhaps a good way to handle this will be to create a kinit utility which fetches the tgt using MSAL. After which everything else will be handled the same as usual. |
This is partially implemented by MR#46. We now have the TGT in the PRT, we just aren't doing anything with it yet (and the tgt is encrypted still). JWE decryption needs to be implemented in compact-jwt for us to get the TGT. |
The cloud and on-prem TGTs are now decrypted and residing within the PRT. Now to just do something with them! |
We can obtain a TGT by authenticating via a ConfidentialClient, then passing the query parameter “tgt=true” during an authentication. Perhaps we can implement a himmelblau kinit command, which will cache the tgt, and a kerberos wrapper library which forwards our kerberos requests via ms-kkdcp.
Description from Steve Syfuhs:
"You’re handed a TGT during AAD auth by appending the query parameter “tgt=true”, and then issue a TGS-REQ using that TGT to https://login.microsoftonline.com/<tenant_id>/kerberos using [MS-KKDCP]."
The text was updated successfully, but these errors were encountered: