Skip to content

Instantly share code, notes, and snippets.

@cleavenworth
Last active February 19, 2025 16:15
Show Gist options
  • Save cleavenworth/7bb9e436c796aa7963476608ab9cfdad to your computer and use it in GitHub Desktop.
Save cleavenworth/7bb9e436c796aa7963476608ab9cfdad to your computer and use it in GitHub Desktop.
LDAP Mapping and Configuration Settings for Okta LDAP > Jamf
LDAP Servers
Connection --
Directory Service: Configure Manually
Server and Port: company.ldap.okta<preview>.com : 636
Use SSL: True
Authentication Type: Simple
Distinguished Username: [email protected],dc=company,dc=okta<preview>,dc=com
Use Wildcards when Searching: True
User Mappings:
Object Class: inetOrgPerson
Search Base: ou=users,dc=company,dc=okta<preview>,dc=com
User ID: uid
Username: uid
Real Name: cn
Email Address: uid
Department: department
Building: o
Position: title
User UUID: entryUUID
Group Mappings:
Object Class: groupofUniqueNames
Search Base: ou=groups,dc=company,dc=okta<preview>,dc=com
Search Scope: All Subtrees
Group ID: uniqueIdentifier
Group Name: cn
Group UUID: entryUUID
User Group Membership Mappings:
Membership Location: Group Object
Member User Mapping: UniqueMember
Use distinguished name of member user when searching the LDAP directory: Enabled
Use the LDAP compare operation when searching the LDAP directory: Disabled
Include member user mapping in returning attributes: Disabled
@seanism
Copy link

seanism commented Sep 29, 2021

What field does Building map to in Okta?

Building: o

@valcparra
Copy link

I have seen 3 different inputs for Group UUID:

  1. entryUUID
  2. objectGUID
  3. uid

I see you have entryUUID. I am not sure which one is correct. Have you seen this?

@taboo8614
Copy link

I can confirm that theses settings work with Jamf Pro and Okta Identity Engine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment