Replies: 1 comment
-
|
It's been a while since I haven't checked this, but when I did, the limitation was that domains had to be set in the app metadata, which are fully static resources. The only domain that would fit the build-time app metadata would be one that's tied to the Passepartout as an app, not the profiles you manage. That's probably why other clients have the same problem. Profiles bear potential info about domains, but such info is only available at runtime, not when I build the app. If that has changed to be set on runtime too (but I hardly doubt so), I'd be happy to improve the app behavior accordingly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Good day community,
the use of a password manager on mobile devices is widespread. To find and display the correct secret, the password manager reads the app's URI, for example, the passepartout app. However, on iOS (iPhone), for some kind of reason it's not possible to read the URI (associated domain) of the OpenVPN app, which is why the secret has to be looked up manually each time. Same behavior with original OpenVPN app.
After a lot of research, I came across this hint: https://community.bitwarden.com/t/how-to-get-uri-for-ios-app/7544/11. Does the app use the correct URI scheme and domain, or is there another solution to this issue? Or maybe just another security setting on the Apple device?
Thank you all for your tips and assistance!
Viktor
Beta Was this translation helpful? Give feedback.
All reactions