Skip to main content
The certificates in your application configuration are RSA encryption keys. You need the private key to sign system user tokens in server-to-server applications and database mirroring. The Developer Portal stores your public key. However, you must store the private key.
There can be only one client secret and only one certificate per environment. To replace a secret or certificate, first click the trashcan to remove the old value and then create a new.

​
How to

  1. In the Developer Portal, go to your app page. To see the list of all apps:
    • Select Apps from the top menu to see all apps across every partner you have access to, or
    • Go to the Applications section of your partner page to see that partner’s apps.
  1. Select Configuration > Authentication. Secrets and Certificates -screenshot
  2. Click New Certificate. New Certificate dialog -screenshot
  3. Enter a description and expiration, and then click Add. Certificates -screenshot
    Expiration date is not enforced yet.
  4. Store the private key somewhere safe! You can’t look it up in the Developer Portal later.
  5. Click Save Settings.
    • If the new certificate is for SOD only: No further action is needed.
    • If the certificate is for stage, production, or all environments: You must request publishing.
When you think it is ready in SOD, you can request to publish to Stage. This starts the certification or validation process, so read the guidelines and be prepared to follow up. The Request to publish button will be disabled with a tooltip that explains what needs to be completed before you can start the process. The SuperOffice app manager or App Store manager will reject or approve. Remember to pick up application keys for all required environments before you request to publish. For custom applications, when you request publish to Stage, we will automatically publish directly to production when approved.

Related topics

Application environmentsIndex