Manage Users

Owned by Alex Xie
Last updated: Oct 07, 2022

Navigate to the /RoleManager URL then click the Users menu. You need a System Admin role to access this page. On this page, you can:

  • Find a user and edit the account detail.

  • Add a new interactive user.

  • Add a new system user.

  • View account status.

  • View the claims assigned to the user.

Create user

Administrator can create two types of user account.  

  • Interactive user account can log on to OneList applications;

  • System user account is designed for APIs. A system user cannot log on to OneList applications. OAuth credentials or API key is configured for system accounts for other systems integrate with OneList APIs. 

The type of account cannot be changed once an account is created. Access permissions are granted to both types of accounts by assigning roles to them.

Assign roles to user

Administrator can assign new roles to the user and remove existing roles from the user. The change will be effective after the user log off and log on again.

Configure OAuth credentials for system account

  • Search the system user then edit its account.

  • Select the Client Credentials tab.

    • Click the Add button will create a new credential row with the client secret is generated automatically.

    • Enter the client id then click the Save button for the row.

    • Click the Show Access Key button to view the client secret.

When applied, the client id is used for identying the source system in OneList.

Generate an API key for system account

  • Search the system user then edit its account.

  • Select the Keys tab.

    • Click the Generate New Access Key button to generate a new key, or click the Show Access Key button to view an existing key;

    • The Allowed clients field is optional. If specified, only the requests made from these IP addresses are accepted;

    • A unique access key must be generated for each source system which integrates with OneList. The key is required to register a source system in OneList. The OneList adapters for that source system use the same key in the HTTP Request header to connect to OneList APIs.