Tutorial: Configure RFPIO for automatic user provisioning
The objective of this tutorial is to demonstrate the steps to be performed in RFPIO and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to RFPIO.
This tutorial describes a connector built on top of the Azure AD User Provisioning Service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory.
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
- An Azure AD tenant.
- A RFPIO tenant.
- A user account in RFPIO with Admin permissions.
Assigning users to RFPIO
Azure Active Directory uses a concept called assignments to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or groups that have been assigned to an application in Azure AD are synchronized.
Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to RFPIO. Once decided, you can assign these users and/or groups to RFPIO by following the instructions here:
Important tips for assigning users to RFPIO
It is recommended that a single Azure AD user is assigned to RFPIO to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.
When assigning a user to RFPIO, you must select any valid application-specific role (if available) in the assignment dialog. Users with the Default Access role are excluded from provisioning.
Setup RFPIO for provisioning
Before configuring RFPIO for automatic user provisioning with Azure AD, you will need to enable SCIM provisioning on RFPIO.
Sign in to your RFPIO Admin Console. On the bottom left of the admin console, click on Tenant.
Click Organization Settings.
Navigate to USER MANAGEMENT > SECURITY > SCIM.
Ensure that Auto User Provisioning is enabled. Click on GENERATE SCIM API TOKEN.
Save the SCIM API Token as this token will not be displayed again for security purpose. This value will be entered in the Secret Token field in the Provisioning tab of your RFPIO application in the Azure portal.
Add RFPIO from the gallery
To configure RFPIO for automatic user provisioning with Azure AD, you need to add RFPIO from the Azure AD application gallery to your list of managed SaaS applications.
To add RFPIO from the Azure AD application gallery, perform the following steps:
In the Azure portal, in the left navigation panel, select Azure Active Directory.
Go to Enterprise applications, and then select All applications.
To add a new application, select the New application button at the top of the pane.
In the search box, enter RFPIO, select RFPIO in the results panel, and then click the Add button to add the application.
Configuring automatic user provisioning to RFPIO
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in RFPIO based on user and/or group assignments in Azure AD.
You may also choose to enable SAML-based single sign-on for RFPIO, following the instructions provided in the RFPIO Single sign-on tutorial. Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other.
To configure automatic user provisioning for RFPIO in Azure AD:
Sign in to the Azure portal. Select Enterprise Applications, then select All applications.
In the applications list, select RFPIO.
Select the Provisioning tab.
Set the Provisioning Mode to Automatic.
Under the Admin Credentials section, input
https://<RFPIO tenant instance>.rfpio.com/rfpserver/scim/v2in Tenant URL. An example value is
https://Azure-test1.rfpio.com/rfpserver/scim/v2. Input the SCIM API Token value retrieved earlier in Secret Token. Click Test Connection to ensure Azure AD can connect to RFPIO. If the connection fails, ensure your RFPIO account has Admin permissions and try again.
In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox - Send an email notification when a failure occurs.
Under the Mappings section, select Synchronize Azure Active Directory Users to RFPIO.
Review the user attributes that are synchronized from Azure AD to RFPIO in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in RFPIO for update operations. Select the Save button to commit any changes.
To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.
To enable the Azure AD provisioning service for RFPIO, change the Provisioning Status to On in the Settings section.
Define the users and/or groups that you would like to provision to RFPIO by choosing the desired values in Scope in the Settings section.
When you are ready to provision, click Save.
This operation starts the initial synchronization of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. You can use the Synchronization Details section to monitor progress and follow links to provisioning activity report, which describes all actions performed by the Azure AD provisioning service on RFPIO.
For more information on how to read the Azure AD provisioning logs, see Reporting on automatic user account provisioning.
- RFPIO does not support groups provisioning currently.
- Managing user account provisioning for Enterprise Apps
- What is application access and single sign-on with Azure Active Directory?