There isn't anything in the web-vault UI regarding SSO as far as i know.
Also, there is nothing in the diagnostics either except for the Generate Support string which will have the variables visible.
But, since you are not using the :testing tagged images, it's logical nothing works. You are using the :latest image, which does not support SSO.
@BlackDex commented on GitHub (Aug 19, 2025):
There isn't anything in the web-vault UI regarding SSO as far as i know.
Also, there is nothing in the diagnostics either except for the Generate Support string which will have the variables visible.
But, since you are not using the `:testing` tagged images, it's logical nothing works. You are using the `:latest` image, which does not support SSO.
There isn't anything in the web-vault UI regarding SSO as far as i know. Also, there is nothing in the diagnostics either except for the Generate Support string which will have the variables visible.
But, since you are not using the :testing tagged images, it's logical nothing works. You are using the :latest image, which does not support SSO.
Same issue here, thanks for the clarification. I’m on the latest tag as well, which explains the 404 on /identity/connect/oidc-signin and why there’s no SSO option in the web vault UI or diagnostics. Do you have an ETA for when the SSO changes will land in latest or a stable release tag? A tracking issue or changelog entry to follow would be super helpful. Thanks again!
@nexaknight commented on GitHub (Aug 19, 2025):
> There isn't anything in the web-vault UI regarding SSO as far as i know. Also, there is nothing in the diagnostics either except for the Generate Support string which will have the variables visible.
>
> But, since you are not using the `:testing` tagged images, it's logical nothing works. You are using the `:latest` image, which does not support SSO.
Same issue here, thanks for the clarification. I’m on the latest tag as well, which explains the 404 on /identity/connect/oidc-signin and why there’s no SSO option in the web vault UI or diagnostics. Do you have an ETA for when the SSO changes will land in latest or a stable release tag? A tracking issue or changelog entry to follow would be super helpful. Thanks again!
Nope. We never had any timeline or roadmap what so ever.
There are a few PR's open, and issues reported which probably need some TLC first before we release it as a stable/latest.
@BlackDex commented on GitHub (Aug 19, 2025):
Nope. We never had any timeline or roadmap what so ever.
There are a few PR's open, and issues reported which probably need some TLC first before we release it as a stable/latest.
So maybe it's good idea to add that information to documentation that SSO works only on testing image. When i came and read documentation in wiki it's look like it's stable and working
@grzonu commented on GitHub (Aug 19, 2025):
So maybe it's good idea to add that information to documentation that SSO works only on testing image. When i came and read documentation in wiki it's look like it's stable and working
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @grzonu on GitHub (Aug 19, 2025).
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
1.34.3
Deployment method
Official Container Image
Custom deployment method
It's container image but in k8s.
Env are set. But there is nothing about SSO in diagnostics, nothing in UI etc.
Reverse Proxy
nginx ingress
Host/Server Operating System
Linux
Operating System Version
Ubuntu 25.04
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Alternatively:
go to https://domain/identity/connect/oidc-signin and you will see 404
Expected Result
Redirect to SSO and login by SSO(Authentik in my case)
Actual Result
Normal login shown
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Aug 19, 2025):
There isn't anything in the web-vault UI regarding SSO as far as i know.
Also, there is nothing in the diagnostics either except for the Generate Support string which will have the variables visible.
But, since you are not using the
:testingtagged images, it's logical nothing works. You are using the:latestimage, which does not support SSO.@nexaknight commented on GitHub (Aug 19, 2025):
Same issue here, thanks for the clarification. I’m on the latest tag as well, which explains the 404 on /identity/connect/oidc-signin and why there’s no SSO option in the web vault UI or diagnostics. Do you have an ETA for when the SSO changes will land in latest or a stable release tag? A tracking issue or changelog entry to follow would be super helpful. Thanks again!
@BlackDex commented on GitHub (Aug 19, 2025):
Nope. We never had any timeline or roadmap what so ever.
There are a few PR's open, and issues reported which probably need some TLC first before we release it as a stable/latest.
@grzonu commented on GitHub (Aug 19, 2025):
So maybe it's good idea to add that information to documentation that SSO works only on testing image. When i came and read documentation in wiki it's look like it's stable and working
@BlackDex commented on GitHub (Aug 19, 2025):
done