I'm sorry, i'm not sure I understand the question. Are you saying that the local users account name is actually set to domainusername? We are using Jamf Connect with Azure and when the local account is created on the MAC it is the same thing we have in Azure for the username, there is no domain added.
@mlawniczak Thanks for the reply. We were using Azure, but were recomended to start using an ADFS native app for several reasons. With this new native ADFS app, users log in with just "username", but when the user folder is created, it gets "DomainUsername". This causes apps like MS Word to fail because they dont know how to escape the character.
Hi @alfredhart We looked into changing the Claim Rule for the the ADFS native app so that when Jamf Connect Login looked for "unique_name" it would return something similar to samAccountName instead of "DomainUsername". This can be done, but required ALOT more testing and approval. We went back to using an ADFS native app, with the Azure options in Jamf Connect, instead of a straight ADFS native app. Each respond back to Jamf Connect Login with a proper token, but when using Azure as the IdP we dont have to pass the "unique_name" to Jamf Connect Login.
Thanks @whitebeer , looked into that as well, we went with the "unsupported" but working way, of Azure IdP and ADFS native app. We needed to change some ADFS settings so that it would allow the User Agent String from Jamf Connect Login to NOT pass a kerberos ticket, but allow Chrome to pass a kerberos ticket, this was a nightmare to figure out but it works now.