If your organization uses Okta to manage employee access to tools and services, you can utilize Okta's Provisioning feature to automatically provide your users with access to DocuWare via SCIM. This guide will walk you through the steps to configure both DocuWare and Okta to set up provisioning for your organization.
With DocuWare 7.12, User Provisioning supports the following provisioning features:
Automatic User Creation: Users assigned to the Reftab application in Okta are automatically created as users in Docuware.
Attribute Synchronization: Any updates to user attributes (userName, email, activeness) in Okta will be reflected in Docuware.
User Deactivation: When users are deactivated in Okta, they are marked as disabled in Docuware, preventing them from logging in.
Register DocuWare in Okta
Login to your Okta organization and navigate to this view:
In the Admin view navigate to Applications > Applications
In the Applications page, click on Create App Integration
In the pop-up, for a sign-in method choose SAML 2.0 and then click Next. This sign-in method is not actually used, but has to be chosen.
In the first tab General Settings on the Create SAML Integration page, enter an app name and click Next.
On the next tab - Configure SAML, enter a Single sign-on URL and an Audience URI. Actual values does not matter, as they are not actually used. You may use http://www.okta.com. Then click Next.
On the Feedback tab, activate the option “This is an internal app that we have created” and click Finish.
In the just created application click on the General tab, on App Setting click Edit, than select SCIM for a provisioning method and click Save.
Scroll down to App Embed Link, then copy the ID after /home/ on the Embed Link - as shown on picture below. Here it is trial-5967756_oktascimintegration_1
Don’t close the Okta configuration and switch to Docuware Configuration.
Connect DocuWare and Okta
Go to DocuWare Configuration > Integration > App Registration.
Select New app registration.
In the Create Application Registration pop-up, choose Web application, then click Continue.
Configure your app registration:
Enter a Name for the app registration
Add a Redirect URL with the value
https://system-admin.okta.com/admin/app/cpc/{ID}/oauth/callback
where ID should be replaced by the value, which you have copied in step 9 above.
In the demo case final URL is
https://system-admin.okta.com/admin/app/cpc/trial-5967756_oktascimintegration_1/oauth/callback
As Grant type select Authorization Code.
In Allowed Resources select User Provisioning.
Confirm with Save.
From the created App Registration copy the values of
Application (Client) ID
Client secret
Switch to DocuWare Configuration > General > User Provisioning.
Activate the option Enable User Provisioning.
In the dropdown Identity Provider select Okta.
In the dropdown Application Registration select the created app registration in the plugin App Registrations (Okta SCIM Integration) (step 6-10 in the chaptre Configurin Okta).
Do not forget to Save.
Copy these links:
SCIM connector base URL
Authorization Endpoint
Access token endpoint URI
Configuring Okta
Switch back to Oka application. Go to Provisioning > Integration > Edit and enter the following inputs:
SCIM connector base URL:
https://usermgmt-testlatest.docuware.cloud/DocuWare/usersyncbackend/okta/scim - copied from step 11.a of the previous chaptre.Unique identifier field for users: userName
Supported provisioning actions:
check Import New Users and Profile Updates, Push New Users, Push Profile Updates, Push Groups, Import GroupsAuthentication Mode: select OAuth 2
Access token endpoint URI: paste the URI copied from 11.c
Authorization endpoint URI → paste the URI copied from 11.b
Client ID: paste the copied in step 5.a
from Configuring DocuWare Application (Client) IDClient Secret → paste the copied in step 5.b
from Configuring DocuWare Authorization endpoint
After saving, navigate back to the Integration tab and at the bottom of the page click the authentication button to generate a token
Provide your DocuWare’s admin user credentials
An updated message will appear ensuring the token is successfully generated
A new App tab should appear under Provisioning tab, on Provisioning to App click Edit, then check Create Users, Update User Attributes, Deactivate Users and Save.
Scroll down to Okta SCIM Integration Attribute Mappings and click on Go to Profile Editor.
5. In the Profile Editor click on Mappings
On each and every mapping except Primary Email > email in the tab Okta SCIM Integration User Profile click on the yellow arrow and select Do not map. When all mappings except the Email one are unset, click Save Mappings at the bottom of the window.
Navigate to the second tab Okta User User Profile and repeat the same procedure for each and every available mapping except Primary Email > appuser.email.
After all mappings except the one for the Username and the one for the Email are unset, you are safe to delete them from Profile Editor by pressing [X] and then Delete Attribute. As a result all Attributes except for Username and Email should be deleted. Username is the only attribute that is required and Email is optional, but should remain mapped in order to receive emails when provisioned.
Action:
Result:
9. Provisioning configurations are all set and you can continue with using it.
Provisioning users
Navigate to the recently created Okta application. Go to Assignments > Assign > Assign to people and then assign a person you want to be provisioned.
Find your successfully created user in DocuWare