You can import users into ºÚÁϺ£½Ç91Èë¿Ú from Namely, provision and manage users in Namely from ºÚÁϺ£½Ç91Èë¿Ú, and use ºÚÁϺ£½Ç91Èë¿Ú Single Sign On (SSO) to give your users convenient but secure access using their ºÚÁϺ£½Ç91Èë¿Ú credentials.
Read this article to learn how to configure the Namely Integration.
Prerequisites
- A ºÚÁϺ£½Ç91Èë¿Ú administrator account
- ºÚÁϺ£½Ç91Èë¿Ú SSO Package or higher or SSO à la carte option
- Contact your Namely account manager or Namely support for instructions on generating a token for use with the integration
- An administrator account in Namely with the appropriate permissions to use the Namely API
- Your Namely subdomain
- Access to the Namely REST API documentation if you will be setting up a custom integration
- To configure SSO, you must have a Namely single sign-on (SSO) enabled subscription
Important Considerations
- You can configure the integration for import only, IdM only, SSO only, or for all 3 capabilities. See the appropriate section(s) below for detailed instructions.
Creating a new ºÚÁϺ£½Ç91Èë¿Ú Application Integration
- Log in to the .
- Go toÌýUSER AUTHENTICATIONÌý&²µ³Ù;ÌýSSO Applications.
- Click + Add New Application.
- Type the name of the application in the Search field and select it.
- Click Next.
- In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.
If this is a Bookmark Application, enter your sign-in URL in the Bookmark URL field.
- Optionally, expand Advanced Settings to specify a value for the SSO IdP URL. If no value is entered, it will default to https://sso.jumpcloud.com/saml2/<applicationname>.
The SSO IdP URL is not editable after the application is created. You will have to delete and recreate the connector if you need to edit this field at a later time.
- Click Save Application.
- If successful, click:
- Configure Application and go to the next section
- Close to configure your new application at a later time
Configuring an Import Only Integration
There are two ways to create an integration that only supports importing users from Namely to ºÚÁϺ£½Ç91Èë¿Ú. You can use the Namely application integration that utilizes SCIM API and protocol and has default field mappings, or you can create a custom integration that utilizes the Namely REST API and allows for custom field mappings.
To configure Namely for importing only
- Create a new application or select it from the Configured Applications list.
- Select the Identity Management tab.
- Click Configure.
- Uncheck Enable management of User Groups and Group Membership in this application.
- Enter the SCIM API Base URL - https://SUBDOMAIN.namely.com/api/scim/v2 (e.g., https://thebestwidgets.namely.com/api/scim/v2 ).
- Enter the Personal Access Token you generated or received from Namely in the Token Key field.
- Click Activate.
- Do not associate any user groups.
- Click save.
Associating user groups will result in user identities being managed by ºÚÁϺ£½Ç91Èë¿Ú in Namely.
Namely User Attributes
SCIM Attribute | ºÚÁϺ£½Ç91Èë¿Ú Attribute | ºÚÁϺ£½Ç91Èë¿Ú UI Value | Notes |
---|---|---|---|
userName | Username | The ‘@.domain.com’ are stripped from the email addressÌý to create the username (e.g., A user with an email of [email protected] will be created with the username toni.mint). | |
emails.work | Company Email | Ìý | |
name.givenName | firstname | First Name | Ìý |
name.middleName | middlename | Middle Name | Ìý |
name.familyName | lastname | Last Name | Ìý |
displayName | displayname | Display Name | If Display Name isn't populated, we use 'First Name' + 'Last Name'. |
addresses.type | addresses: type[=work] | Work Address | . |
addressed.streetAddress | addresses: streetAddress | Work Street Address | Ìý |
addresses.locality | addresses: locality | Work City | Ìý |
addresses.region | addresses: postalCode | Work State | Ìý |
addresses.postalCode | addresses: postalCode | Work Postal Code | Ìý |
addresses.country | addresses: country | Work Country | Ìý |
phoneNumbers.[obj] | phoneNumbers: type [=work phone 'business'] phoneNumbers: number | Work Phone | Ìý |
active:true | state | User State | User state value will be either ‘Staged’ or ‘Active’Ìý based onÌý the value set for Application / Directory Integrations in Settings>User Management> Default User State for User Creation. |
active:false | state | User State | User state will be set to suspended. |
userType | employeeType | Employee Type | Ìý |
title | jobTitle | Job Title | Ìý |
employeeNumber | employeeIdentifier | Employee ID | Ìý |
organization | company | Company | Ìý |
department | department | Department | Ìý |
costcenter | costCenter | Cost Center | Ìý |
To create a custom Namely integration for importing only
- Create a new application or select it from the Configured Applications list.
- Select the Identity Management tab.
- Click Custom API.
- Select Bearer token as the Authentication method.
- Enter the Namely REST API Base URL - https://SUBDOMAIN.namely.com/api/v1 (e.g., https://thebestwidgets.namely.com/api/v1 ).
- Enter the Token Key you generated or received from Namely.
- Enter profiles in the Resource Location field.
- Enter /profiles in the Endpoint Path field.
- Select Body for Response Parameter Location.
- Enter meta.total_count for the Response Body JSON Path.
- Enter per_page for the Limit Name.
- Enter page for the Offset Name.
- Click Test Connection.
- If the test connection fails, an error notification will slide out and the specific errors will show in the configuration. Please review the error messages. You may need to review the documentation or work with Namely support based on the error.
- If the test connection is successful, a success notification will slide out and User Schema Attribute Mapping fields will appear.
- Enter id in the Unique ID field.
- In the Service provider attribute JSON path field, enter email for both the ºÚÁϺ£½Ç91Èë¿Ú attributes Company Email and Username.
Click Preview to see a list of the JSON returned from Namely to complete your mappings and to verify that correct information will be added in ºÚÁϺ£½Ç91Èë¿Ú.
- Click Add attribute to map any other desired attributes you want to import from Namely to ºÚÁϺ£½Ç91Èë¿Ú.
- Click the trash can icon to delete any attributes you don’t want imported.
- Click Preview to verify that all the mapped information will be returned to ºÚÁϺ£½Ç91Èë¿Ú.
- Click Activate.
- Click save.
Example mappings for suggested attributes
Configuring the Identity Management Integration
Use this option if you want ºÚÁϺ£½Ç91Èë¿Ú to be the source of truth for your identities, or if you want a bi-directional sync between ºÚÁϺ£½Ç91Èë¿Ú and Namely. Configuring identity management and associating user groups to the Namely application allows you to provision, update, and deprovision users from the ºÚÁϺ£½Ç91Èë¿Ú Administrator Portal to Namely. Every change made to user attributes in ºÚÁϺ£½Ç91Èë¿Ú will result in that same change being made to the user profile in Namely. You can also import users.
- Create a new application or select it from the Configured Applications list.
- Select the Identity Management tab.
- Click Configure.
- Uncheck Enable management of User Groups and Group Membership in this application.
- Enter the SCIM API Base URL - https://SUBDOMAIN.namely.com/api/scim/v2 (e.g., https://thebestwidgets.namely.com/api/scim/v2 ).
- Enter the Token Key you generated or received from Namely.
- Click Activate.
- Add user groups that contain users you want to provision and manage from ºÚÁϺ£½Ç91Èë¿Ú in Namely. See the Authorize User Access section below for details.
Are you a visual learner? Watch our video.
Importing Users
This functionality is helpful if users have already been created in the application but have not been created in ºÚÁϺ£½Ç91Èë¿Ú.
- Log in to the .
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application and click to open its configuration panel.
- Select the Identity Management tab.
- Click manual import.
- Select the users you want to create in ºÚÁϺ£½Ç91Èë¿Ú from the application from the list of users that appear. Users in the list have two import statuses:
- NewÌý- user has not been imported
- ImportedÌý- user has been imported and has an account in ºÚÁϺ£½Ç91Èë¿Ú
Tip: Try using the New Users-only filter when selecting users to import. This will move all of your new users to the top of the list, making them easier to identify and select.
- Click import.
- If you are importing less than 100 users, your import results will display in real time and you can continue onboarding your usersÌý
- If you have more than 100 users being imported, ºÚÁϺ£½Ç91Èë¿Ú will send you an email when your import is complete
- You can now connect and grant users access to all their ºÚÁϺ£½Ç91Èë¿Ú resources. Learn more in the Authorize Users to an Application and Connecting Users to Resources articles.
Warning: Imported users must be members of a user group bound to an application for ºÚÁϺ£½Ç91Èë¿Ú to manage their identity in, and access to, the application.
SCIM Directory Insights Events
The following Directory Insights (DI) events provide visibility into failures and detailed information about the user and group data being added or updated from HR or other external solutions to ºÚÁϺ£½Ç91Èë¿Ú.
Customers with no package or the Device Management Package will need to add the Directory Insights à la carte option. Directory Insights is included in all other .
SCIM DI Integration Events
Event Name | Event Description |
---|---|
idm_integration_activate | Logged when an IT admin attempts to activated new SCIM Identity Management integration. |
idm_integration_update | Logged when an IT admin attempts to update a configured and activated SCIM Identity Management integration. |
idm_integration_reauth | Logged when an IT admin attempts to change the credentials for an activated SCIM Identity Management integration. |
idm_integration_delete | Logged when an IT admin attempts to deactivate an activated SCIM Identity Management integration. |
SCIM DI User Events
Event Name | Event Description |
---|---|
user_create_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to create a new user in service provider application. |
user_update_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to update an existing user in service provider application. |
user_deprovision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to change an existing user to inactive in the service provider application. |
user_delete_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to delete an existing user in service provider application. |
user_lookup_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú encounters an issue when trying to lookup a user to determine if the user needs to be created or updated. |
SCIM DI Group Events
These DI events will only be present if SCIM Groups are supported.
Event Name | Event Description |
---|---|
group_create_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to create a new group in service provider application. |
group_update_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to update an existing group in service provider application. |
group_delete_provision | Logged when ºÚÁϺ£½Ç91Èë¿Ú tries to delete an existing group in service provider application. |
Configuring the SSO Integration
To configure ºÚÁϺ£½Ç91Èë¿Ú
- Create a new application or select it from the Configured Applications list.
- Select the SSO tab.
- In the SP Entity ID field, update the URL with your specific Namely subdomain.(e.g., https://thebestwidgetsnamely.com/saml/metadata).
- In the ACS URL field, update the URL with your specific Namely subdomain - https://SUBDOMAIN.namely.com/saml/consume (e.g., https://thebestwidgetsnamely.com/saml/consume).
- In the field terminating the IDP URL, either leave the default value or enter a plaintext string unique to this connector.
- Select save.
Download the certificate
- Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
- Select the SSO tab and click IDP Certificate Valid > Download certificate.
The certificate.pem will download to your local Downloads folder.
To configure Namely
- Log in to your Namely company site as an administrator.
- In the toolbar on the top, click Company.
- Click the Settings tab.
- Click SAML.
- Click Enable SAML.
- In the Identity provider SSO URL textbox, paste the value of the ºÚÁϺ£½Ç91Èë¿Ú IDP URL.
- Browse to, open and copy the contents of the certificate.pem downloaded in the previous section.
- Paste it into the Identity provider certificate textbox.
- Click Save.
Authorizing User SSO Access
Users are implicitly denied access to applications. After you connect an application to ºÚÁϺ£½Ç91Èë¿Ú, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel.
To authorize user access from the Application Configuration panel
- Log in to the .
- Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
- Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
- Select the check box next to the group of users you want to give access.
- Click save.
To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.
Validating SSO user authentication workflow(s)
IdP-initiated user workflow
- Access the
- Go toÌýApplications and click an application tile to launch it
- ºÚÁϺ£½Ç91Èë¿Ú asserts the user's identity to the SP and is authenticated without the user having to log in to the application
SP-initiated user workflow
- GoÌýto the SP application login - generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO
This varies by SP.
- Login redirects the user to ºÚÁϺ£½Ç91Èë¿Ú where the user enters their ºÚÁϺ£½Ç91Èë¿Ú credentials
- After the user is logged in successfully, they are redirectedÌýback to the SP and automatically logged in
Removing the Integration
These are steps for removing the integration in ºÚÁϺ£½Ç91Èë¿Ú. Consult your SP's documentation for any additional steps needed to remove the integration in the SP. Failure to remove the integration successfully for both the SP and ºÚÁϺ£½Ç91Èë¿Ú may result in users losing access to the application.
To deactivate the IdM Integration
- Log in to the .
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
- Click confirm.
- If successful, you will receive a confirmation message.
To deactivate the SSO Integration or Bookmark
- Log in to the .
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Select theÌýSSO or BookmarkÌýtab.
- Scroll to the bottom of the configuration.
- Click Deactivate SSO or Deactivate Bookmark.
- Click save.
- If successful, you will receive a confirmation message.
To delete the application
- Log in to the .
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to delete.
- Check the box next to the application to select it.
- Click Delete.
- Enter the number of the applications you are deleting
- Click Delete Application.
- If successful, you will see an application deletion confirmation notification.