Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The left field denotes the Zilla fields and the right one denotes the fields from the API response.

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 true as active status so the value for this config would be true and for Okta, we get PROVISIONED so the value for this config would be PROVISIONED.

Below configuration are for OAuth based generic application:

  • Authorization UrlURL: The endpoint for the authorization server, used to get the authorization code. Example: For Okta it is https://{orgdomain}/oauth2/v1/authorize. Token UrlIf you are going for Authorization code based OAuth generic application then you have to specify the authorization URL. Otherwise if your are going for Client Credential Based OAuth in that we can leave it blank.

  • Token URL: The endpoint for the authentication server. This is used to exchange the authorization code for an access token. Example: For Okta it is https://{orgdomain}/oauth2/v1/token.

  • Client Id: The client Id issued to the client during the application registration process.

  • Client Secret: The client secret issued to the client during the application registration process.

  • Space separated scopes: The scope of the access request. It may have multiple space-delimited values.

Info

Redirect URIs:

  1. If its  a authorization code flow kind of OAuth then redirect URI will be https://app.zillasecurity.com/api/auth/callback/genericoauth

  2. If its a client credential based OAuth then redirect URI will be https://app.zillasecurity.com/api/auth/callback/genericclientcredoauth

9. Click Next/Sync now to start the sync.

...