Was released 2 days ago: https://github.com/bitwarden/web/releases/tag/v2.16.0
SSO Will not work without server-side changes.
We probably have to implement a lot of code to support this.
Only updating the web-vault will not do the trick.
SSO Will not work without server-side changes.
We probably have to implement a lot of code to support this.
Only updating the web-vault will not do the trick.
I've looked into it, the server-side changes are actually quite minimal. Their implementation is basically comparable to a reverse proxy in front of bitwarden (but integrated), it does not replace the normal login and master-password requirements.
Some more info:
https://github.com/bitwarden/server/commits/fd6b10df564778ea73c00e8dcecc00aa74c5eb7d/src/Core/Enums/SsoType.cs
https://bitwarden.com/help/article/getting-started-with-sso/
It would play into my hands if that were to be implemented. But I can only support the statement of Ornias1993.
Everyone can create a PR to implement this 馃槈.
Would be nice to have this, including all lot of other stuff.
When someone has time to implement this it will probably be pushed and merged.
This would be huge if added correctly!
To keep the issue tracker more focused, I'm closing this issue in favor of the meta issue at #246
@BlackDex Besides the fact that it has nothing to do with a docker image needing to be pushed.
Most helpful comment
I've looked into it, the server-side changes are actually quite minimal. Their implementation is basically comparable to a reverse proxy in front of bitwarden (but integrated), it does not replace the normal login and master-password requirements.
Some more info:
https://github.com/bitwarden/server/commits/fd6b10df564778ea73c00e8dcecc00aa74c5eb7d/src/Core/Enums/SsoType.cs
https://bitwarden.com/help/article/getting-started-with-sso/