Start a conversation

Resolving Unauthorized Errors in the O&S Service

Overview

When attempting to create an order using the O&S service, you may encounter an unauthorized error. This issue often arises due to a wrong certificate name in custom settings or if the user making the request is not properly authorized. It is crucial that the certificate used matches the one sent during provisioning—regardless of where it is used in settings. Matching certificate names across settings is only relevant if Solution Management (SM) is also in use.

Information

To resolve the unauthorized error when using the O&S service, follow these steps to ensure the configuration is properly set:

  1. Log in to your Salesforce org.
  2. Navigate to Setup, go to the Custom settings, and manage 'Asynchronous Messaging Options' custom setting.
  3. Verify the certificate name listed in this setting. It must be the name of the provisioned certificate used for this org.
  4. If you are also using Solution Management, navigate to the 'SM Options' custom setting.
  5. If 'SM Options' exists, ensure the certificate name listed there matches the one in 'Asynchronous Messaging Options'. Update it if necessary.
  6. Save the changes and test the O&S service to confirm the issue is resolved.

Frequently Asked Questions

What causes the unauthorized error in the O&S service?
The unauthorized error is typically caused by using a certificate name that does not match the one provisioned for the org or if the user(s) is not properly authorized for the service.
How do I update the certificate name in 'Asynchronous Messaging Options'?
Log in to your Salesforce org, go to Setup, access the Custom settings, manage the 'Asynchronous Messaging Options' custom setting, and ensure the certificate name matches the one that was sent during provisioning.
What if I’m not using Solution Management?
If Solution Management is not in use, the 'SM Options' custom setting may not be available, and only the certificate in 'Asynchronous Messaging Options' needs to be validated.
What should I do if the issue persists after updating the certificate name?
If the issue persists, ensure that all other related settings and configurations are correct. If you created a new certificate, make sure a provisioning request was sent with the new public key before updating settings. You may also need to consult the user guide for service connectivity or contact support for further assistance.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments