Closed sandervandegeijn closed 10 months ago
Hey,
For the identifier it's normal the default front-end is what is expected to be merged. I patched the frontent for a better flow but you need to pass an env variable: cf https://github.com/Timshel/vaultwarden#docker
For your issues on IOS I see nothing strange in the logs, I have no ios device so I probably won't be able to debug it sorry.
The SSO override is a nice touch, much more user friendly! Didn't see the SSO identifier screen anymore either. Will ask a colleague that hasn't used it to try it as well tomorrow.
I reinstalled the iOS version of BW, same problem. I made a video but I need a little time to blur out all the sensitive data. Will do that tomorrow (since it's 23:12 over here now).
Thanks for the effort!
I have also encounter the same issue on both iOS device and android device. After logging in the webview, it's not redirected back to the mobile app but instead opening the web vault in the webview.
Ok, I think I know where the regression is, will test-it with android.
1.30.1-2
is building and should fix the issue.
will test again, thanks!
can confirm the latest build works on iOS and android devices
I'm running the tag 1.30.1-2. Adding the new as a second account besides my normal account doesn't give the redirect error anymore. But on iOS I'm back at
I'm also a bit confused where the MDT Integration Services text came from, I only used that as an organisation name.
I'm also a bit confused where the MDT Integration Services text came from, I only used that as an organisation name.
As soon as the application has an email (first field with no front modification or after identification) it tries to check if it's associated with an Organization.
Hm okay, feels a bit weird but it works I guess :)
Hm okay, feels a bit weird but it works I guess :)
:), it's useful because if an user is already part of an organization (invitation or group/org mapping) then things like the org password policy can be applied when the user create his master password.
Edit: And from BitWarden point of view it's even more important since in the official server the sso is configured at the organization level and not globally.
Edit: And from BitWarden point of view it's even more important since in the official server the sso is configured at the organization level and not globally.
I'm not sure I understand this entirely, for Vaultwarden it will be either enabled or disabled right?
The redirect issue has been solved, but on iOS I'm back at:
I saw there was a new image: oidcwarden/vaultwarden-oidc:testing Used that one to test this.
Hey,
I'll close this since the original issue is working I believe. If IOS is still broken, maybe open another issue.
Sure will test it as soon as there are docker containers with all the new fixes :)
Great thanks!
Running the latest tag from oidcwarden/vaultwarden-oidc:latest at monday 8th Jan 20:39 CET:
Bitwarden app on mac
iOS app:
This wasn't there before. On iOS the login flow is also broken when adding a new account, after this screen it will ask for the master password in the popup webview and if you fill in that, you are logged in but not in the app, but in the webview that's opened for the login flow. The app doesn't get logged in.
In the browser it's working correctly.
Deployment environment
Install method: Docker on k8s
Clients used: web, ios, android
Reverse proxy and version: nginx ingress
MySQL/MariaDB or PostgreSQL version: postgres 16
Other relevant details:
Steps to reproduce
add a new account to the bitwarden app
Expected behaviour
User doesn't know what to fill in, this will lead to questions. Screen should be skipped.
Actual behaviour
Screen is shown
Troubleshooting data
^^