You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When setting up RomM (version 3.7.0) for OpenID Connect (OIDC) authentication via Synology SSO, the error {"detail":"Email is not verified."} appears, preventing successful login. The email address used in Synology SSO is the same as the one configured for the local RomM user.
The following steps have been attempted:
Creating a new RomM user with the same email address used in Synology.
Verifying the client ID, client secret, redirect URL, and OIDC provider URL.
Confirming that the well-known configuration is fetched from https://<my_domain>/webman/sso/SSOOauth.cgi.
Despite these efforts, the error persists:
ERROR: [RomM][base_handler][2025-01-05 14:45:27] Email is not verified.
192.168.0.1:0 - "GET /api/oauth/openid?code=XXX&state=XXX HTTP/1.0" 400
To Reproduce
Below is an excerpt from the docker-compose.yml file:
The OIDC email verified check now fails if the email is explicitly
unverified, or if the `email_verified` claim is supported and the email
is not explicitly verified.
Previously, the OIDC implementation failed for any OIDC provider that
did not include the `email_verified` claim in the userinfo response.
Providers like Synology do not include this claim, so the check always
failed with error "Email is not verified."
I haven't found a formal specification for the `email_verified` claim,
and how it should be handled, but this implementation should be more
robust and work with more OIDC providers.
Fixes#1446.
RomM version
Docker 3.7.0
Describe the bug
When setting up RomM (version 3.7.0) for OpenID Connect (OIDC) authentication via Synology SSO, the error {"detail":"Email is not verified."} appears, preventing successful login. The email address used in Synology SSO is the same as the one configured for the local RomM user.
The following steps have been attempted:
Creating a new RomM user with the same email address used in Synology.
Verifying the client ID, client secret, redirect URL, and OIDC provider URL.
Confirming that the well-known configuration is fetched from https://<my_domain>/webman/sso/SSOOauth.cgi.
Despite these efforts, the error persists:
To Reproduce
Below is an excerpt from the docker-compose.yml file:
Provider Configuration (Synology SSO)
Any advice or troubleshooting ideas on how to resolve the “Email is not verified” error would be greatly appreciated.
The text was updated successfully, but these errors were encountered: