Login for Firefox plugin failed

Morph€us
Hi,

I never logged in succesfully with the firefox plugin.
The server doesn't accept my username password combo. It's a bit strange because I'm able to login to my wbsite account.
What's wrong?

Here my report ID: D993729010

thanks
  • dstillman
    What's wrong?
    I'm going to go out on a limb and say your username. It should work, obviously, but there's a pretty good chance that's the issue.

    Try with your email address instead.
  • dstillman
    edited October 15, 2014
    (And the next major version of Zotero will handle authentication differently, so this should stop being an issue. Anything that works to log into the website will work in the client too.)
  • Amun-Re
    Okay it's very easy. The system doesn't accept the character "€". I think only ASCII-characters will be accepted.
  • dstillman
    Well, as I said, you could just use your email address — there was no need to create a new account.
  • dstillman
    edited October 21, 2014
    Though I guess it was probably the right call, since honestly you're generally asking for trouble using an extended character in a username. Even something like generating a URL slug often wouldn't work properly. (Your user page here ended up as "morphus".)
  • aurimas
    you're generally asking for trouble using an extended character in a username. Even something like generating a URL slug often wouldn't work properly. (Your user page here ended up as "morphus".)
    How is that even an issue these days? Besides, if it is, these sort of checks should be done during registration, so I'm not sure it's reasonable to say that the _user_ made an unwise choice.
  • dstillman
    How is that even an issue these days?
    Because the slug generator still strips them, presumably because when it was written extended characters in URLs tended to either not work or end up percent-encoded. And changing it now might be somewhat of an ordeal.
    these sort of checks should be done during registration, so I'm not sure it's reasonable to say that the _user_ made an unwise choice.
    Well, as I said above, this of course should work, and registration should catch it if doesn't, but that doesn't mean using extended characters in a username is a particularly good idea or that there won't be unexpected bugs in one of the many disparate systems on different technical stacks that make up a site's services. (In our case, the login issue is that the current version of the client still uses HTTP Basic Auth for file syncing. That will change with the new sync architecture.) And since Morph€us was obviously a rather elective choice — rather than, say, trying to use one's real name — I'm just pointing out that one should not be too surprised when problems occur.
  • aurimas
    In our case, the login issue is that the current version of the client still uses HTTP Basic Auth for file syncing. That will change with the new sync architecture.
    That would also be an issue for passwords as well (something that I thought we said was working, but I must be mistaken then). In any case, we do encodeURIComponent the username/password in the client, which would make them compatible with HTTP basic auth and should be losslessly decoded on the server (sort of, at least this should be good enough for Zotero, since we know the string was a UTF-8 string to start with).

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.