Closed shall1024 closed 3 years ago
It seems like the Beaker code searches for users in LDAP while attempting to create accounts; if the account exists in the LDAP server then the error occurs, otherwise, it does not. (I tried creating a user with a username NOT registered via ipa manually and it worked).
The problem was that the LDAP domain was incorrect in server.cfg
, so enough information was made available to allow users already present in ipa
to log in, but NOT to create new users that were registered in ipa.
I'll email Afom back and update our internal documentation in case this error comes up in the future.
This issue stems from Afom's login issue we discussed over email.
When attempting to create a new user in Beaker, a 500 Internal Server Error is thrown.
If you login with using credentials from the LDAP server, Beaker is supposed to create a new user from the information given there, but instead, it throws a 500 Internal Server Error. This does NOT occur if a user that already exists tries to log in.
If you try to create the user manually in Beaker, the same error occurs.
This is the error in
server_debug.log
, when you try to create the account in either scenario:Currently trying to figure out how to handle this KeyError/why it might be occurring. We've definitely been able to create user accounts via LDAP before, let alone, manually, so I'd be surprised if it's really a problem with the Beaker code.