Jitsi-meet: placeholder="[email protected]" is confusing

[ulab]

Description

After enabling LDAP authentication we had multiple people who tried to enter their full email address as username since the login popup asks them for [email protected] while they need to just enter their username.

Current behavior

placeholder="[email protected]"

Expected Behavior

placeholder="username" - probably internationalized as "Benutzername" in German, since you also ask for "Benutzerpasswort"

Possible Solution

Fix the placeholder to a more generic value

Steps to reproduce

Enable authentication and create a room.

Environment details

Debian 10, Jitsi debian package 1.0.4101-1, Firefox 74.0 on MacOS.

[saghul]

When using XMPP authentication with more than one host, however, the domain must be specifiedd. I don't think there is a one-size-fits-all placeholder. The UI does not know what auth type is used either.

[ulab]

I feel that just "Username" or "User identity" is more generic, since it could be either?

But if you suggest something that looks like an email address, people will always try to enter that.

I don't know the code much, but searching the repository for "[email protected]" I get two results. One of them seems to make a difference by switching between user identity and [email protected] depending on wether config.hosts.authdomain is set?

    const placeholder = config.hosts.authdomain
        ? 'user identity'
        : '[email protected]';

Since authdomain defaults to config.hosts.domain, the first choice will never hit, will it?

[SignoreMic]

Same problem here!
What do you mean with "XMPP authentication with more than one host" ?
I have configure the host needs authentication (AD), guests don’t ...

[RyanColp]

Same issue here. I set up LDAP authentication on my server, and the current placeholder confuses my users too.

It would be useful if the placeholder could be customised, perhaps with the addition of a new setting in interface_config.js.

[slackluis]

Same problem here!
It would be useful if the placeholder could be customized.

[ovailleau]

Hi !
Same problem for me. I'm using ldap with ActiveDiectory and "sAMAccountname".
Users have to enter their short login (not login@domain). The placeholder text is a little bit confusing !
Until I can't customize thi stext, I cannot deploy Jitsi-meet into my organisation.

It would be useful if the placeholder could be customized.
Thanks a lot

[SignoreMic]

Dear all,
I had found [email protected] in the file app.bundle.min.js and customized it with "Username".
Works for me, but I'm not sure it is the best way to do it.
Saluti

[RyanColp]

Thanks SignoreMic.

Editing app.bundle.min.js worked for me as well, and seems to be a good temporary workaround. Be prepared to redo the customization though, as app.bundle.min.js will probably be overwritten by upgrades.

[webslider]

Hi there !
For those who don't want to edit app.bundle.min.js, here is a workaround using MutationObserver that I've put in my /usr/share/jitsi-meet/plugin.head.html :

<script>
var observer = new MutationObserver(function (mutations, me) {
  if(!window.APP.conference.isJoined()){
    var canvas = $('input[name ="username"]').length;
        if (canvas) {
          $('input[name ="username"]').attr('placeholder', 'login');
          return;
        }
  }
  else {
    me.disconnect(); // we joined a conference, stop observing
  }
});

$(document).ready(function() {
  // start observing
  observer.observe(document, {
    childList: true,
    subtree: true
  });
});
</script>

[ovailleau]

It works like a charm.
I just replaced the text by "Compte Windows" (that's sound better in french) instead of 'login' at line 6.
Thanks a lot !

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jlusky]

This still needs to be fixed

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[freaky-m0]

Same problem here... our staff tries to login with e-mail daily and then get stuck at "connecting...". Is there a "better" way than customizing our html or js file? That will get lost every time we update.