Single Sign-On with JWT (Cloudflare Access)
SickRock can trust a signed JWT added by an authenticating reverse proxy, such as Cloudflare Access. Users who reach SickRock through the proxy are signed in automatically, without using the SickRock login page.
Add an auth block to config.yaml in the /config volume (or the directory given by -configdir / SICKROCK_CONFIGDIR):
auth:
jwt:
certsUrl: "https://<team>.cloudflareaccess.com/cdn-cgi/access/certs"
issuer: "https://<team>.cloudflareaccess.com"
aud: "<Access application AUD tag>"
claimUsername: "email"
header: "Cf-Access-Jwt-Assertion"
cookieName: "CF_Authorization"
-
certsUrlis the JWKS endpoint used to verify the token signature.pubKeyPath(RSA public key file) orhmacSecretcan be used instead. -
issuerandaudmust match the token claims. -
claimUsernameis the claim used as the SickRock username. -
headerandcookieNamesay where the token is read from; set either or both.
Restart SickRock after changing config.yaml. The startup log shows httpauthshim: JWT header authentication enabled (and … cookie …) when it is active.
Users
The first time a JWT user visits, SickRock creates their account automatically (created_by: sso-autocreated) and adds it to the Everyone group. Grant further roles or groups from the IAM pages, as for any other user. Usernames are matched exactly, so an existing local account with the same username (for example the email address) is used as-is.
Signing out and switching accounts
Signing out of a JWT session does not end the proxy’s session. Instead SickRock sets a sickrock-sso-off cookie in that browser, and ignores the JWT while it is present. This shows the login form, so you can sign in with a username and password (or another method) instead.
To go back to the JWT user, choose Single Sign-On on the login page. This clears the cookie and signs you in from the proxy again.
Only enable this when SickRock is reachable solely through the authenticating proxy, and always set issuer and aud.
|