Ability to create a client credential accepting a public key

[mendhak]

Checklist

• [x] I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

Hi team, we're interested in using the client credential feature Private Key JWT Authentication.

From what I can tell, the Auth0 Deploy CLI allows setting a client credential for an application by pointing at its key ID.

  "client_authentication_methods": {
    "private_key_jwt": {
      "credentials": [
        {
          "id": "cred_12345"
        }
      ]
    }
  },

But it does not allow actually passing those public keys so we can create credential IDs.

Feature request is to allow us to also specify the public keys here so that we don't really have to pass a specific credential ID.

Describe the ideal solution

Ideal solution - we pass up to 2 maximum public keys strings for a client application, and Auth0 Deploy CLI manages creating and managing it. When we remove a key and replace it with another, Auth0 Deploy CLI manages removing the old one and putting the new one in place. This is a nice way to rotate client credentials.

Totally made up:

  "client_authentication_methods": {
    "private_key_jwt": {
      "credentials": [
        {
          "public_key_1_name": "my_first_key",
          "public_key_1_body": "----BEGIN PUBLIC KEY---......"
        },
        {
          "public_key_2_name": "my_new_key",
          "public_key_2_body": "----BEGIN PUBLIC KEY---......"
        }
      ]
    }
  },

Alternatives and current workarounds

I'm not sure what to do

Additional context

No response

[kushalshit27]

Hi, Thanks for the feature request! We'll evaluate how to incorporate it 🤝 and follow up if we need more details.