Share This Article
Do you need to make more information about users available through LDAP?
Now, you have a better way to build and manage user profiles through a new series of user attributes. By having a wider array of information you can store in JumpCloud about a user, you can better centralize their definition in your organization and allow other external resources to consume this valuable data.
New Attributes have been added to the user object to include employment data, as well as other personal information:
| EMPLOYMENT DATA | PERSONAL INFORMATION |
|---|---|
| Job Title | Middle Name |
| Department | Display Name |
| Cost Center | Description |
| Location | |
| Employee ID | |
| Employee Type | |
| Company |
With these attributes at your disposal, you can resolve many of the issues that vex you and your IT Admin’s day to day. Now, you can use Job Title to determine if a user is an engineer, a VP, or an intern. You can use Employee ID to store badge numbers for cross reference to physical access systems. You can use Company to identify users who are vendors and Employee Type to identify contractors. You can even use the flexible Description to add notes about users, and many more use cases.
Once stored in JumpCloud, these attributes will propagate to the user’s record within JumpCloud’s LDAP service, allowing other resources to pull and leverage that information directly from LDAP or JumpCloud’s RESTful API.
| JUMPCLOUD | LDAP |
|---|---|
| Job Title | title |
| Department | departmentNumber |
| Cost Center | businessCategory |
| Location | physicalDeliveryOfficeName |
| Employee ID | employeeNumber |
| Employee Type | employeeType |
| Company | company |
| Middle Name | initials |
| Display Name | displayName |
| Description | description |
With this rich directory of user data available to LDAP consumers, you can improve your workflow and provide more value to your users.
As an example, now your PBX system displaying department and title information about callers will make it easier for your users to decide whether to answer or let the call go to voicemail. Now, your ticketing application can import Display Name for use as a preferred name, so that your users know your support engineer as Phil, which he prefers, instead of his legal name of Philipé, which only his grandmother calls him.
In summary, with these new attributes, your authoritative JumpCloud directory is a more powerful and useful place to to build and manage user profiles, allowing you to better centralize their definition in your organization, and use that information where you need it.
To get started, you can read more about this update in our Knowledge Base, learn how to populate these attributes using the JumpCloud RESTful API for the systemuser object, and keep on the lookout for a continued series of features related to this exciting new implementation.
