On This Page
Okta Admins can upload their own SAML certificates to sign the assertion for Outbound SAML apps and to sign the AuthN request and decrypt the assertion for Inbound SAML.
Note: Okta as a SAML Service Provider is referred to as Inbound SAML. Okta as a SAML Identity Provider (IdP) is referred to as Outbound SAML.
To use your own SAML certificate, update the key credential for the affected apps or IdPs.
The general procedure is the same for both the Outbound and Inbound SAML applications. However, some of the API calls are different as described in the steps below. The general procedure contains the following steps:
- List your apps
- Generate a certificate signing request (CSR)
- Sign the CSR
- Publish the CSR
- Update the key credential for the app to specify the new certificate
- Clone the certificate (optional)
- Upload the new certificate to the ISV
For information on using the Postman REST API test client for these steps, see Get Started with the Okta REST APIs.