Versions Compared

Version Old Version 40 New Version 41
Changes made by

Chad Fay

Chad Fay

Saved on

Key

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

...

When an Identity Provider (IDP) creates unique IDs for users, deleting and recreating a user in the IDP results in a new unique ID for that user. If you add the recreated user back into Avigilon Alta, the system will recognize them as a new user due to the new ID, even though the email address is the same. This can cause confusionconfuse, as it becomes unclear which version of the user is correct.

...

Info

Note:
If a user is manually inactivated in the Alta Access system, they will remain inactive regardless of Identity Provider updates until they are manually reactivated from within the Alta Access system.

Avigilon Alta currently does not support the following Okta provisioning features but may do so in the future:

  • Sync Password

  • Groups > Push Now

  • Remove Users *

* Note: Users are not removed from the Avigilon Alta application; they are only deactivated.The push now feature in Okta is not currently supported

Prerequisites

To use this application, your account must meet the following requirements:

  • Have one of these Avigilon Alta licenses:

    • Okta Advanced

    • Premier User Management

  • Admin access to your Okta organization is required to configure SCIM.

Supported features

The SCIM service supports the following capabilities:

  • Create Users: Users assigned to the Avigilon Alta application in Okta are eligible for synchronization with Avigilon Alta.

  • Update User Attributes: Changes made to user attributes in Okta are propagated to the Avigilon Alta application.

  • Deactivate Users: When users are deactivated in Okta, this status is reflected in the Avigilon Alta application.

  • Group Push: Groups and their members in Okta can be pushed directly to the Avigilon Alta application.

Okta Advanced app set up and configure

...