#CODA 2 TUTORIALS UPDATE#

If you choose to change the matching target attribute, you will need to ensure that the Coda API supports filtering users based on that attribute.

#CODA 2 TUTORIALS UPDATE#

The attributes selected as Matching properties are used to match the user accounts in Coda for update operations. Review the user attributes that are synchronized from Azure AD to Coda in the Attribute-Mapping section. Under the Mappings section, select Synchronize Azure Active Directory Users to Coda. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box. If the connection fails, ensure your Coda account has Admin permissions and try again. Click Test Connection to ensure Azure AD can connect to Coda. Under the Admin Credentials section, input your Coda Tenant URL and Secret Token retrieved earlier in Step 2. Select Enterprise Applications, then select All applications. To configure automatic user provisioning for Coda in Azure AD: This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users in TestApp based on user assignments in Azure AD. Configure automatic user provisioning to Coda When scope is set to all users, you can specify an attribute based scoping filter. When scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app. Test with a small set of users before rolling out to everyone. If the only role available on the application is the default access role, you can update the application manifest to add additional roles. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. When assigning users to Coda, you must select a role other than Default Access. If you choose to scope who will be provisioned based solely on attributes of the user, you can use a scoping filter as described here. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users to the application. The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user.

Define who will be in scope for provisioning Learn more about adding an application from the gallery here. However it is recommended that you create a separate app when testing out the integration initially. If you have previously setup Coda for SSO you can use the same application. Add Coda from the Azure AD application galleryДЄdd Coda from the Azure AD application gallery to start managing provisioning to Coda. If there is no Bearer Token, click Generate New Token. Note the SCIM Base URL and SCIM Bearer Token. Open your Organization Admin Console by selecting Organization Settings under the. Configure Coda to support provisioning with Azure AD

Determine what data to map between Azure AD and Coda.

Determine who will be in scope for provisioning.

Learn about how the provisioning service works.

A Coda Enterprise administrator account.Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). A user account in Azure AD with permission to configure provisioning (e.g.The scenario outlined in this tutorial assumes that you already have the following prerequisites: Keep user attributes synchronized between Azure AD and Coda.Remove users in Coda when they do not require access anymore.

Coda 2 tutorials