You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Android app > Settings > Server URL, if I try to input a server url that includes basic credentials (e.g. https://user:pass@meet.mydomain.com/) the app automatically changes the url to remove the username and password (e.g. https://meet.mydomain.com/).
Expected Behavior
The server url should be able to handle http basic username/password values in the server url.
Possible Solution
Enable HTTP basic auth support for the mobile apps in server urls.
Steps to reproduce
Create a basic username password file.
echo "myuser:mypassword" > /path/to/my.htpasswd
Add HTTP basic authentication to the default nginx config so that users are asked to authenticate
The mobile apps are not browsers, thus they won't repond to HTTP auth. If you want to protect your deployment with authentication you should use XMPP authentication, which Jitsi Meet supports: https://github.com/jitsi/jicofo/#secure-domain
Description
When adding HTTP basic access authentication to the nginx config, the server url in the mobile app settings removes the credentials and does not work. However, the authenticated server url works perfectly when using a desktop browser. Also discussed here: https://community.jitsi.org/t/enabling-http-authentication-using-docker-jitsi-meet/32797/2
Current behavior
In the Android app > Settings > Server URL, if I try to input a server url that includes basic credentials (e.g.
https://user:pass@meet.mydomain.com/
) the app automatically changes the url to remove the username and password (e.g.https://meet.mydomain.com/
).Expected Behavior
The server url should be able to handle http basic username/password values in the server url.
Possible Solution
Enable HTTP basic auth support for the mobile apps in server urls.
Steps to reproduce
Environment details
Tested on Android app 20.2.3 build 4129209
The text was updated successfully, but these errors were encountered: