Versions Compared

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 *

  • Import Users/Groups

* Note: Users are not removed from the Avigilon Alta application; they are only deactivated.

Info

Note: If you are using Groups in Okta to manage your users please read this doc as Okta prescribes a certain way to handle this scenario.

Prerequisites

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

  • Have these Avigilon Alta licenses:

    • Premium or Enterprise

    • Okta Advanced

  • 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.

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

Okta Advanced app set up and configure

...

  1. Go to Okta > Applications

  2. Browse App Catalog

  3. Search for and select Avigilon Alta

  4. Add integration

  5. Navigate to the General tab and choose SCIM under Provisioning.Switch to the Provisioning tab and click Integration.Provisioning tab

  6. Select Configure API Integration

  7. Enable the checkbox labeled Enable API integration

  8. Enter the following SCIM Connection settings:

  9. In the Authorization section, paste the token from Alta Access.

  10. Checkbox Import Groups must be unchecked as it is not supported.

  11. Test the connection configuration and click Save.

  12. Return to your Okta Advanced app and continue from step #7 above.

SCIM advanced mapping

...

Use the JSON editor to create rules for HTTPS requests that map users from the identity provider to a role or a specific group or all groups in Alta Access.

Iframe
srchttps://info.openpath.com/hubfs/Openpath/images/kustomer-articles/advanced_mapping.png
width650
frameborderhide
titleSCIM advanced mapping
alignmiddle
height177
longdescSCIM advanced mapping

...