Skip to main content

Hello All

I am having an issue where our local usernames are being setup as "first.last" and this is causing issues down the provisioning road. We are using OneLogin with JAMF Connect and have the LDAP attributes pulling as well, below are the attrbitutes currently mapped

UserID - uSNCreated

USername- sAMAccountname

RealName - GivenName

usersUUID - uidNumber

 

I changed these attributes and it seems this could be the cause but im not sure. Attributes that were in Attribute mappings before the change when the names came in as "firstlast" correct format

UserID - not mapped

username - cn

real name - givenname

usersUUID - UidNumber

 

Just wanted to get some advice on what could be causing this, these are the only things ive changed lately

If the local username is being created as first.last, I don't think it will have to do with your LDAP settings. Jamf Connect is creating the local user during PreStage enrollment. You could try to provide Identity Provider Attribute Mappings in your Enrollment Customization settings, if you are using that. There's a good post here on how to set it up:

https://www.jamf.com/blog/how-to-configure-jamf-connect-in-jamf-pro/

If the local username is being created as first.last, I don't think it will have to do with your LDAP settings. Jamf Connect is creating the local user during PreStage enrollment. You could try to provide Identity Provider Attribute Mappings in your Enrollment Customization settings, if you are using that. There's a good post here on how to set it up:

https://www.jamf.com/blog/how-to-configure-jamf-connect-in-jamf-pro/


It was the Jamf connect + OneLogin connector we use pulling the username that way, basically its setup by design that way so we will just be leaving it alone. Thanks for the help

Reply


Terms & ConditionsCookie settings