> No and no. > > There are independent bits and pieces of a bigger puzzle that need to be > worked on, they are done by different groups but altogether they > contribute to the same goal. Most of the specifications aren't > written yet or not documented publicly so regardless of the projects > being done, discovering all that information is crucial.
As Alexander said, I'm not working on SSSD, but really on learning all the bits, how they go together, and what we need to do as a community. Right now the Samba team is investigating and working on a proof of concept. We know now how to join to Azure AD, and I have figured out how to request a PRT (Primary Refresh Token) with a partial Kerberos TGT. There is a protocol that needs implemented before we can do anything with that TGT, IIUC. If you're able to help with implementation in SSSD, I can point you in the right direction for documentation, etc. -- _______________________________________________ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
