|
Untrusted self-signed X509 certificates can cause Postman to render a blank screen without further errors. In order to run Postman against a SSL URL with a self-signed certificate, add the certificate to the operating system trusted certificates repository on the machine running Postman. On Windows, this is usually the Trusted Root Certification Authorities store. On Linux, this is a file of PEM certificates called /etc/ssl/certs/ca-bundle.trust.crt.
|
Property | Value | ||
Token Name | Use any preferred name. | ||
Grant Type | Authorization Code | ||
Callback URL | Set this equal to the <es-redirect-uri> parameter: <es-base-url>/ExperienceService/auth/oidc/callback For example: https://es.example.com:8443/ExperienceService/auth/oidc/callback For more information, see SSO Configuration Parameters. | ||
Auth URL | Set this equal to the <as-auth-endpoint> parameter. For example: https://pingfed.example.com/as/authorization.oauth2 For more information, see SSO Configuration Parameters. | ||
Access Token URL | Set this equal to the <as-token-endpoint> parameter. For example: https://pingfed.example.com/as/token.oauth2 For more information, see SSO Configuration Parameters. | ||
Client ID | Set this equal to the Experience Service OAuth client ID that you defined in your OpenID provider. | ||
Client Secret | Set this equal to the Experience Service OAuth secret. | ||
Scope | THINGWORX
| ||
State | This can be left blank. | ||
Client Authentication | Send client credentials in body |
Since the access token may expire after a short period of time, proceed with Experience Service installation immediately after obtaining the token. |