mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-01 11:19:52 +03:00
Allow SSO OIDC Issuer Redirect #2457
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hofq on GitHub (Dec 7, 2025).
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN, SSO_ENABLED, SSO_ALLOW_UNKNOWN_EMAIL_VERIFICATION, SSO_CLIENT_ID, SSO_CLIENT_SECRET, SSO_AUTHORITY, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD
Config:
Vaultwarden Build Version
testing branch latest
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Browser Extension, Web Vault, Desktop, Android, iOS
Client Version
No response
Steps To Reproduce
Get an 301 Moved Permanently Error, cause of Dynamic Routing inside of Nextcloud
Enter Issuer url /intex.php/
Get Failed to discover OpenID provider: Validation error: unexpected issuer URI
https://hostname/(expectedhttps://hostname/index.php)"Expected Result
I would expect the App to dynamically resolve Redirects or add a Flag for that
or be able to specify openid-configuration directly
Actual Result
I get 2 Errors
Logs
Screenshots or Videos
No response
Additional Context
https://github.com/H2CK/oidc/issues/400
@SadmL commented on GitHub (Jan 1, 2026):
https://github.com/H2CK/oidc/issues/474#issuecomment-2406671034
@stefan0xC commented on GitHub (Jan 4, 2026):
I think this issue could be resolved by updating our documentation to also mention the OIDC App for Nextcloud and mention this specific rewrite fix to account for limitation of the app (though this should probably be added in their wiki as well). I don't think this is something that we should address by writing a custom http client as the OpenID specification does not allow 301 redirects or a different path for this endpoint (this is also why this probably will not be supported by the maintainer of the
openidconnect-rscrate that we use).@SadmL commented on GitHub (Jan 4, 2026):
Thing is there is no need to do such stuff, for example, for Matrix Synapse, Forgejo, GoToSocial, it works without these rewrites.
(I'm not a dev/programmer, and this is by no means a complaint)
@stefan0xC commented on GitHub (Jan 4, 2026):
Yeah, but it seems like that is because the libraries they use are less strict about getting a resource. Synapse for example uses
authlibwhich is usingtreqthat by default allows redirects (and the same seems to be true for go's default http client) whileopenidconnect-rsas mentioned just allows200which might be less user-friendly but is straightforward and conforming to the spec.