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 no longer sync through Okta.
The push now feature in Okta is not currently supportedremain inactive regardless of Identity Provider updates until 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. Sign in to your account:

  2. Navigate to App Marketplace > Get Apps.

  3. Click the Okta Advanced tile.

  4. Select + Get App Organization.

  5. Go to App Marketplace > My Apps.

  6. Click the pencil icon to edit the Okta Advanced app.

  7. Under Sync Type, select SCIM.

  8. Click Generate Auth Token, copy the token, and click Done.

    • Note: You will use this token during SCIM setup in Okta (Step 9).

  9. Set up SCIM in your Okta portal.

  10. After setting up SCIM in Okta:

    • Manually trigger the first sync in the Okta portal.

    • Refresh the Access Groups or Roles page in Alta Access.

  11. Enable any of the following settings as needed:

    • Auto-create mobile credential: Automatically creates a mobile credential for every user.

    • Auto-create cloud key credential: Automatically create a cloud key credential for every user.

    • Sync mobile phone numbers: Syncs user phone numbers in E.164 format (maximum 15 digits, e.g., +[country code][subscriber number]).

    • Enable single sign-on (SSO) for portal access: Allows Okta super admins to log in to Avigilon Alta Access using Okta credentials.

    • Enable single sign-on (SSO) for mobile app: Enables users to log in to the Openpath app using Okta credentials.

  12. If you haven’t created any Avigilon Alta access groups yet, go to Users > Access Groups and create them.

  13. Use the Create Access Group Mapping button to map Okta groups to Avigilon Alta Access groups.

...

Follow these steps to set up the SCIM integration:

  1. In the left-hand menu, go to Applications and select Applications.

  2. Click Create App Integration, choose SAML 2.0, and click Next to complete the SAML setup workflow.Go to Okta > Applications

  3. Browse App Catalog

  4. Search for and select Avigilon Alta

  5. Add integration

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

  7. Select Configure API Integration

  8. Enable the checkbox labeled Enable API integration

  9. Enter the following SCIM Connection settings:

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

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

  12. Test the connection configuration and click Save.

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

...