Each issuer publishes a discovery document and a JWKS so an external cloud can validate assertions CrushFTP signs. Reference an issuer from a VFS item of type OAuth with the grant type Federation (OIDC).

Add Remove

    Issuer

    Generated, and fixed. Put the same value in the VFS item's OIDC Server ID.


    Replace domain.com with the public host the cloud can reach. Until you do, this issuer serves nothing. The host needs a TLS certificate from a public CA with its full chain served, which is the server's own SSL certificate under Encryption.

    Leave blank unless a reverse proxy publishes CrushFTP under a sub-path. It only changes the Issuer URL; what this server accepts comes from the listener's ReverseProxy Path under IP / Servers.

    Show what this issuer publishes

    Field Value
    Where it is published

        The cloud fetches these endpoints anonymously, before any login, so publish the issuer only on the listener that is actually reachable from the internet. "All" publishes it on every HTTP(S) port.

        Signing key

        CrushFTP generates and stores this issuer's RSA signing key itself, so there is nothing to configure here. The key is created when the issuer is added and deleted when it is removed.

        Signs Key name Key type Signature algorithm Created Thumbprint (kid) Stored at
        Key rotation

        Step 1: add a new key Step 2: remove the old key

        The key needs no name, no CA and no expiry date, and no scheduled replacement. Replace it only if it may have been exposed, or if a policy requires it: add the new key, wait an hour for the cloud to refresh its cached key list, then remove the old one. Step 1 changes nothing; step 2 hands over.

        Reset To Default Cancel Save