OAuth Configuration
The UDEP supports connection to a number of backend systems and authentication models. While most REST APIs support Basic Auth, API Token or a simple custom authentication model, SAAS solutions such as Salesforce, Google etc support OAuth as a secure method of authentication. The advantage with OAuth ofcourse being that your credentials are never known to the platform and only an authentication token (and a refresh token) are saved which can be revoked anytime.
The UDEP supports OAuth with the following systems:
- Azure AD
- Box
- Dropbox
- DocuSign
- Live (Microsoft)
- Salesforce
- ServiceNow
What this means to you is any of your mobile or web applications that connect to these systems can take advantage of the UDEPs OAuth capability to authentication your users.
Configuration
Section titled “Configuration”- Edit the Port properties and navigate to the Authentication Type parameter
- AUTHENTICATION_TYPE: Set the authentication type to OAuth V2
- OAUTH_PROVIDER: Select the system you are authenticating with
- OAUTH_SCOPE: Set the OAuth scope that you require. To get the correct values and the access that is required please refer to the provider’s documentation and copy over the Scope string
- OAUTH_CLIENT_ID: The OAuth ClientID (API Key) for this provider. Refer to the provider’s documentation to create a connected app and copy over the Client ID (also called as API key)
- OAUTH_CLIENT_SECRET: The provider system will also generate a Client Secret (along with the ID above) and needs to be copied over. Do not share this elsewhere.
Now that the OAuth is configured, whenever the system needs to be accessed with a token, UDEP will automatically send a link for the user to authenticate from the Service provider and save the required tokens. Tokens will also be automatically refreshed on expiry. In case tokens are revoked, UDEP will prompt the user for authentication again.