What changes
Set it up
The example uses Authentik athttps://auth.example.com.
1
Create the application in your provider
Create an OAuth2 or OpenID Connect application of the confidential type, with:
Copy the client ID, the client secret, and the authorization, token and userinfo endpoints. In Authentik they are
https://auth.example.com/application/o/authorize/, .../token/ and .../userinfo/.2
Set the variables
The userinfo response has to include
sub and email.3
Recreate the container and try it
Recreate the app container so it reads the new values. A plain The database, Redis and Temporal keep running. Avoid
docker restart or
docker compose restart keeps the old container and its old environment.In the folder that holds docker-compose.yaml, recreate only the postqueen service:docker compose down for a settings change: on
a host that runs other Compose services in the same project, it stops them too. On Kubernetes, see
Kubernetes with Helm.The sign-in screen shows your provider’s button, and signing in lands you in PostQueen.
If it does not work
The provider says the redirect URI is invalid
The provider says the redirect URI is invalid
The redirect URI registered at the provider is not exactly
FRONTEND_URL + /settings: check the scheme, the host and that there is no trailing slash.Sign-in comes back and fails
Sign-in comes back and fails
The backend log has the reason.
POSTQUEEN_OAUTH environment variables are not set means one of the five URL and credential variables is empty. Token request failed quotes your provider’s error, usually a wrong secret or a client that does not accept the secret in the request body.Related
- Configuration reference: every sign-in button and what shows it
- Deploy to a server: closing sign-up with
DISABLE_REGISTRATION