Open topic with left hand navigation
Proliance can be configured as an OpenID/OAuth 2.0 Authorization Server. When set up this way, Proliance can allow registered third-party applications to access its resources without requiring that users share their Proliance credentials with the third party application.
Configure Proliance as an OpenID/OAuth server using the Proliance Local Admin application on the Proliance server. To configure one or more external apps as an OAuth client, use the Proliance WebUI. For more on the steps required to configure a Proliance server as an OAuth Authorization server, see the Proliance Administration Guide.
Proliance Administrators who configure external apps to use OAuth must have OAuth Configuration permission assigned to their role.
|
TIP:
|
To add and modify an OAuth client
Name. Enter a name for the custom application.
Client ID. This is a unique ID generated by Proliance and cannot be entered by the user. This string will be used by the custom application when requesting an access token from Proliance.
Enabled. Select to enable OAuth binding for this custom application.
Flow. Choose a method for OAuth binding: Select Implicit for desktop applications and Code for Web server-based applications.
Proliance Log Off Ends Application Session. Select this option if you want the access token for the OAuth client cleared when you log off from the Proliance WebUI.
Secret. A randomly-generated string for use as the Consumer Secret in the custom application. The custom application must keep the secret confidential.
Redirect URL Location. Enter the URL to which Proliance should redirect after authenticating a user using the custom application.
Access Token Lifetime Override. Enter a threshold time limit, in seconds, when an access token will expire.
Refresh Token Lifetime Override. Enter a threshold time limit, in seconds, when a refresh token will expire. This option is only visible if you choose Code flow instead of Implicit.