# Change signing certificate,

**URL:** <https://devforum.okta.com/t/change-signing-certificate/15924>\
**Category:** Questions\
**Created:** [September 3, 2021, 9:19pm UTC](https://devforum.okta.com/t/change-signing-certificate/15924 "2021-09-03T21:19:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bazzaa](https://avatars.discourse-cdn.com/v4/letter/b/e47774/32.png) [@Bazzaa](https://devforum.okta.com/u/Bazzaa)\
**Post date:** [September 3, 2021, 9:19pm UTC](https://devforum.okta.com/t/change-signing-certificate/15924/1 "2021-09-03T21:19:43Z")

</div>

My app uses OpenID Connect.  
I created the certificate, then updated the app to use newly created kid using /credentials/keys. What I expect is that /keys?client\_id={id} endpoint returns a key with kid equals to what I’ve created and tokens are signed/verified with a private/public key pair OKTA created for me as result of that certificate update. But /keys contains absolutely different kids and token validation fails.

What is wrong here? Maybe I’m misunderstanding the purpose of /credentials/keys? Maybe it would work ok only in certain context?

Documentaton says:  
**Note:** When using a Custom Authorization Server, you may work with a client that can’t call the `/keys` endpoint to dynamically fetch the JWKS. You can pin that specific client to a specific key by [generating a key credential](https://developer.okta.com/docs/reference/api/apps/#generate-new-application-key-credential) and [updating the application](https://developer.okta.com/docs/reference/api/apps/#update-key-credential-for-application) to use it for signing. This overrides the Custom AS rollover/pinning behavior for that client. Should you need to turn off automatic key rotation for the entire Custom Authorization Server, you can do that by switching the **Signing Key Rotation** value to **Manual** in the Admin Console.

Appreciate any help, thank you!

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [September 3, 2021, 9:45pm UTC](https://devforum.okta.com/t/change-signing-certificate/15924/2 "2021-09-03T21:45:20Z")

</div>

Are you trying to validate Access Tokens issued by the Org Authorization Server (issuer = [https://org.okta.com](https://org.okta.com))?

---

<div class="post-metadata">

**Author:** ![Bazzaa](https://avatars.discourse-cdn.com/v4/letter/b/e47774/32.png) [@Bazzaa](https://devforum.okta.com/u/Bazzaa)\
**Post date:** [September 3, 2021, 9:56pm UTC](https://devforum.okta.com/t/change-signing-certificate/15924/3 "2021-09-03T21:56:21Z")

</div>

No, issuer is [https://dev-19951857.okta.com/oauth2/default](https://dev-19951857.okta.com/oauth2/default). Also /default/v1/keys?client\_id={} does not reflect changes I did creating and updating certificate.

---

<div class="post-metadata">

**Author:** ![Bazzaa](https://avatars.discourse-cdn.com/v4/letter/b/e47774/32.png) [@Bazzaa](https://devforum.okta.com/u/Bazzaa)\
**Post date:** [September 4, 2021, 8:27am UTC](https://devforum.okta.com/t/change-signing-certificate/15924/4 "2021-09-04T08:27:07Z")

</div>

In fact the certificate update works well with [https://dev-19951857.okta.com/oauth2](https://dev-19951857.okta.com/oauth2) and [https://dev-19951857.okta.com/oauth2/v1/keys?client\_id={id}](https://dev-19951857.okta.com/oauth2/v1/keys?client_id=%7Bid%7D) returns expected kid and I’m able to verify signed token by using that key. Given that Manual Rotation for application is enabled (it is disabled by default).

But I expect same behaviour for [https://dev-19951857.okta.com/oauth2/](https://dev-19951857.okta.com/oauth2/) **default**. [https://dev-19951857.okta.com/oauth2/](https://dev-19951857.okta.com/oauth2/) **default** /v1/keys?client\_id={id} returns different key set. How to make it possible for default auth server to apply the keys provided with certificate while signing tokens?

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [September 24, 2021, 12:15am UTC](https://devforum.okta.com/t/change-signing-certificate/15924/5 "2021-09-24T00:15:42Z")

</div>

Are you saying the keys for the default server (issuer = [https://org.okta.com/oauth2/default](https://org.okta.com/oauth2/default)) vary from the ones for the Org server (issuer = [https://org.okta.com](https://org.okta.com))?

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [February 8, 2024, 7:26pm UTC](https://devforum.okta.com/t/change-signing-certificate/15924/6 "2024-02-08T19:26:56Z")

</div>

Closed on February 8, 2024, 7:26pm UTC


