-
Notifications
You must be signed in to change notification settings - Fork 472
500 Internal server error when Duplicate entry #1302
Comments
I'm getting a bit lost here 😕 Could you go step by step how you have reproduced this ? I've tried the following:
What am I missing ? |
OK
|
@aleksejlopasov just to be sure, could you paste your LDAP config, just in case you are using email guessing or something 😉 |
Will it be enough to post my portus_ldap_* env vars? Because in my case everything is configured via env vars |
@aleksejlopasov sure. Also note that we have the
|
@mssola Here it is, man ;-)
I think email guessing is not necessary when using ldap because email attribute is received from ldap-server |
When creating users on LDAP, make sure that the email won't clash. If that was to happen, then set the email to nil so the user has to enter the email manually. Fixes SUSE#1302 Signed-off-by: Miquel Sabaté Solà <[email protected]>
PR #1306 should fix this situation. |
Thanks, man. You're the best=) |
When creating users on LDAP, make sure that the email won't clash. If that was to happen, then set the email to nil so the user has to enter the email manually. Fixes #1302 Signed-off-by: Miquel Sabaté Solà <[email protected]>
Hi,
I've tried these docker-containers https://github.com/openSUSE/docker-containers for my production purposes and found an issue with authentication in versions 2.1 and 2.2 (2.0 seems to be working fine but I need version not older then 2.1 for new features)
Service is integrated with LDAP server.
When I login into web UI using ldap credentials, everything works, but if I try to login using with the same email_address, I get a mysql duplicate error. It's ok - I understand the email_address record must be unique.
BUT...
In version prior to 2.1 I've got code 401 from ActiveRecord and a page "sign_in" code 200 with a message "Email has already been used":
In versions 2.1 and 2.2 I've got 500 Internal server error:
Is it code bug or my loss?
Please help to fix that
The text was updated successfully, but these errors were encountered: