This functionality was modified in an update. For more information, see Edit the Web Client configuration (modified in an update).
-
Navigate to the Web Client virtual directory and open the settings.json file. For example:
C:\SDx Server Files\SDxWebClient_Sites\WebClientSite\settings.json
-
Edit the following values in the authorization section:
Setting |
Detail |
---|---|
AUTHORIZATION_CLIENT_ID |
0oag04x1t1cW5miJS0h7 |
AUTHORIZATION_REDIRECT_URI |
https://okta-spf.12345.com/spfwebclient/ |
AUTHORIZATION_POSTLOGOUTREDIRECT_URI |
https://okta-spf.12345.com/[separatelogoutURLpath] |
AUTHORIZATION_IDENTITYPROVIDER |
"" |
AUTHORIZATION_SCOPES |
ingr.api openid profile |
AUTHORIZATION_USEPKCE |
True |
AUTHORIZATION_DUMMYCLIENTSECRET |
"" |
You must ensure the AUTHORIZATION_REDIRECT_URI is entered exactly as shown in the
detail, including trailing forward slashes.
The following example shows the flat layout of a Web Client settings.json file:
{
"AUTHORIZATION_CLIENT_ID": "SDAClient",
"AUTHORIZATION_DUMMYCLIENTSECRET": "DTygPREwre;lmnq3p(*Olyf5;wiWLB:loCda8Lrn3Y_)",
"AUTHORIZATION_IDENTITYPROVIDER": "F96D415C-FBE6-4A9F-A631-DAODD406AD3B",
"AUTHORIZATION_POSTLOGOUTREDIRECT_URI": "http://host:4200/",
"AUTHORIZATION_REDIRECT_URI": "http://host:4200/",
"AUTHORIZATION_USEPKCE": true
}
Using the Server Manager settings
In Server Manager, you can use the Logout Redirect URL setting to provide a separate redirection path after logout to avoid OAuth authentication loops. For more information, see Post logout redirect authentication loop.
You can also configure the settings.json file using the Server Manager command line
syntax. The following example demonstrates how to configure the command line using
the Server Manager settings as follows:
SDxServerManager.exe /updatesdasite sn:SDxClient /oauthissuerurl: https://dev597594.oktapreviewcom/oauth2/ausg0871hp0DCijdr0h7 /clientid:0oag04x1t1cW5miJS0h7 /oauthredirecturi:https://okta-spf.12345.com/spfwebclient /postoauthRedirecturi:https://okta-spf.12345.com/[separatelogoutURLpath] /scopes:”ingr.api openid profile” /identityprovider:""