Provision and manage users without an email ID

The managed users workflow is used in special cases to support alternate authentication methods by setting up a username and a temporary PIN on behalf of users who do not use their e-mail IDs. An administrator is responsible for onboarding the user to the system and sets up a server-generated PIN for each user. The temporary PIN can be delivered to the users through preferred message delivery systems like SMS.

When should you use the managed users workflow?

• Your application is a legacy system that does not collect e-mail IDs for user registration
• Your users cannot access emails for verification and authentication

As an example, a legacy fleet management system that manages fleet data including manage driver data and other features to support drivers. However, the legacy system does not collect its drivers’ email IDs as part of the onboarding system.

Basic managed user flow

To onboard users to the Profiles system and enable them to use Trimble Identity sign-in, use the following API operations.

Prerequisites:

• Must have one or more accounts already set up in your system
• Should have admin user identified for the managed users

A basic managed user workflow follows these steps:

• Step 1: Create an account with Profiles. The account name must match with the account that’s already in your system.
• Step 2: Create a managed user group. The user who creates a managed user group becomes the administrator of the group by default.
• Step 3: Add a user to the managed user group. The user name and a temporary password of the user are passed in the Request Body while adding the user to the managed user group.
• Step 4: Change a user’s PIN.

For a complete list of APIs supported in the managed users workflow, see the Profiles API definition.

Password policy for creating a managed user

• Minimum characters expected - 8 chars
• Maximum characters allowed - 16 chars
• Allowed combination - Alphanumeric. Special chars are not allowed.