...
| Info |
|---|
Note: If the Zilla fields and the fields from the API response are the same then this configuration property can be left blank. |
Account Active Statuses (e.g. Active, Enabled): To map your active account status, specify what value(s) indicate an ACTIVE account. All other accounts will be marked as INACTIVE. Values should be comma separated in case of multiple values.
Authorization URL:
Token URL: If you are going Authorization code based or client credential based OAuth then it is mandatory to specify token URL.
Client ID: Client id of the connector that you have created for Zilla for that application.
Client Secret: Client secret of the connector that you have created for Zilla for that application.
Space separated scopes: Space separated scopes required to sync application.
Required Fields
The following fields are required in the API Integration:
id: a unique identifier value assigned to an account. Example = 1234
username: a unique display name assigned to an account. Example = jsmith
email: a unique email addressed assigned to an account. Example = jsmith@yourcompany.com
status: a value that indicates if an account is Active or Inactive. Example = ‘Active’, ‘Inactive’, ‘Enabled’, ‘Disabled’
roles: the permissions associated with an account. Example = ‘Admin’, ‘Default’, ‘Standard’
Account Active Statuses: The status (active or inactive status) response from the API. Value could be true, enabled, active, provisioned, etc. Examples: For AHA we get
trueas active status so the value for this config would betrueand for Okta, we getPROVISIONEDso the value for this config would bePROVISIONED. Values should be comma separated in case of multiple values.
Below configuration are for OAuth based generic application:
...