> ## Documentation Index
> Fetch the complete documentation index at: https://docs.junojourney.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Signing key for the in-app launcher

> Generate the Portal SSO signing secret your backend uses for in-app launcher tokens, switch Portal SSO on, and rotate the secret without downtime.

The [in-app launcher](https://docs.junojourney.com/admin/in-app-launcher.md) has no key of its own: your backend signs every launcher token with your organization's Portal SSO signing secret. An admin generates the secret in Juno, switches Portal SSO on, and gives your developers three values.

> [!NOTE]

***

## Create the key

**1. Open Portal SSO**

Go to **Admin** > **Security** > **Developer Settings**, and find the **Portal SSO** section.

**2. Generate a secret**

Under **Signing secrets**, select **Generate secret**, then **Generate**. Copy the **Key ID (kid)** and the **Signing secret**. The secret is shown only once, so copy it before you select **Done**.

**3. Copy your tenant ID**

Under **Integration details**, copy the **Tenant ID (JWT aud)**.

**4. Switch Portal SSO on**

Turn on the switch, so it reads **Portal SSO enabled**. You can switch it on once a secret exists.

**5. Hand the three values to your developers**

Store the secret, its key ID, and the tenant ID in your backend's secret manager, where your developers' token route reads them. The secret never goes into browser code. See [Install the in-app launcher](https://docs.junojourney.com/integrations/in-app-launcher.md#step-1-sign-tokens-on-your-backend).

![Portal SSO in Developer Settings, with the Portal SSO enabled switch, a signing secret, and the integration details](https://mintcdn.com/juno-76d1c392/gwAXT9S7xzD2Vtjs/images/integrations/portal-sso-developer-settings.png?fit=max\&auto=format\&n=gwAXT9S7xzD2Vtjs\&q=85\&s=1e7e20e8875a0c85a92b816b45552ad8)

> [!WARNING]
>
> While Portal SSO is off, Juno refuses every launcher token, and your users see no button. Switching it off later hides the launcher for everyone.

***

## Two secrets at most

Your organization can have two active signing secrets at once, each with its own key ID. Tokens signed with either one work, for the launcher and for Portal SSO. With two secrets, Juno says so and asks you to delete one before you generate another.

The second secret is there for rotation: you switch your backend to a new secret before you delete the old one, so the launcher never stops.

## Rotate the secret

**1. Generate a second secret**

In **Portal SSO**, select **Generate secret**. Copy the new secret and its key ID. Two secrets are now active.

**2. Switch your backend**

Your developers sign with the new secret and put its key ID in the `kid` header.

**3. Delete the old secret**

On the old secret, select the delete icon, then **Delete** to confirm. Anything still signing with it stops working right away, and you can't undo this.

While Portal SSO is on, you can't delete your only secret. Generate its replacement first.

> [!WARNING]
>
> The same secret also signs [Portal SSO](https://docs.junojourney.com/integrations/portal-sso.md) hand-offs, which can sign in any user in your organization at their own role, admins included. Keep it on your backend only. If it's ever exposed, generate a new one, switch your backend to it, and delete the exposed one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.