Configure OAuth Support for the REST APIs

Oracle B2C Service Knowledge Advanced REST APIs support OAuth 2.0 authorization for staff accounts and contact users. Developers can create applications that use OAuth tokens from Oracle Identity Cloud Service (IDCS) or other Identity Providers to authorize staff accounts or contact users.

To enable agent user authorization using the OAuth 2.0 authorization framework, you must configure Knowledge Advanced to accept OAuth tokens from an identity provider as follows:

1. Retrieve a signing certificate for your application.
2. Navigate to the Knowledge Advanced Configuration page in your Information Manager Console.
3. Select Tools, System, Configure, and OAuth Identity Provider Configuration.
4. Select the Enable use of OAuth Tokens from Identity Provider check box.
5. Enter the URL of the identity provider in the OAuth Identity Provider URL for validating OAuth token textbox.
6. Copy the signing certificate from Step 1 and paste it in the textbox under OAuth Signing Certificate used for validating OAuth tokens.

   Note:

   The certificate must be in Privacy Enhanced Mail (PEM) format as shown in the following example.

   Example

   -----BEGIN CERTIFICATE-----
   MIIDQzCCAiugAwIBAgIGAU+7bWHIMA0GCSqGSIb3DQEBCwUAMFExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjEhMB8GA1UECxMYaWRlbnRpdHkub3JhY2xlY2xvdWQuY29tMQ8wDQYDVQQDEwZHbG9iYWwwHhcNMTUwOTExMDgwMjMxWhcNMjUwOTExMDgwMjMxWjBRMRswGQYDVQQKExJPcmFjbGUgQ29ycG9yYXRpb24xITAfBgNVBAsTGGlkZW50aXR5Lm9yYWNsZWNsb3VkLmNvbTEPMA0GA1UEAxMGR2xvYmFsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxWVFlx+E925RYQjPnKpKtHLqUonJMI1/xyM1f4Orly9RzpcaXX7ajEkgMAzffL3rsvBQkPLmO0vHIHs4KNdWoVUmbLZerjDdfLZQl3FZuXcZKXtzVOLyBVt2SNp/k23VgyGN7+8tiAJWC9SFIPBdWD8U2dxqM9izSEn9pvoMyR5iyaEoZepazJQPLysrF23g1/gI8Bo2EUAHdO5atfGfT2YQbZPSOBWiq09QYwMRBuI0Ye0TI3GwYs1x3/2LoporOj+fkYCl4ki4JK2ifwk+TA5o29cdNSuSoA7rTZL3u+dNw0c6OPxvnW6LtCn4RpieZTh7W2sYLg8ozBwd3PHNTwIDAQABoyEwHzAdBgNVHQ4EFgQUi9Fzo9g57klDG3Kv0nK+8IhbtrIwDQYJKoZIhvcNAQELBQADggEBAKx9sZvbGiQnbO/BfgdlXwloqwjZHT3Byr91Pqp0zXrdg/QaUMIOiJQ8A85d5ptccpgNrYzIukSdFUzRP0kugyNzdFXBZ9/muhSkiFBdfBBdEwqXprdZBHcwWng9t2iww4tvzVhw06ZcIYyGUo8/e8erXmiOt9WeFhi7utQg+gyKw01RvaP73ApCpMuQjxTh7QgQNh02Xo+1QStYLFGcv+ZqHhTZwqOndZiQ68t7JcbGaZmNMxKwR4Z1go+RZ+4Ffa8d9rH1OiXWNB6ukGawQdcfZWNlUWcA7ntRSCfKP5UeDcNpHBDCVZSTvnpAEB42jiTuRuWfuA5Lq0rTDxapmzI=
   -----END CERTIFICATE-----
   

7. Click Save.

Now, staff accounts or contact users can use OAuth tokens for authorization.