New Account Fails to be Created in Database - Temp Email?

I’m trying to get a new account to log in - obviously it’s not working, hence the topic.

Server side:
September 14, 2018 12:59: (LDAP) Error saving user [ldap identity] (temp-email-for-oauth-[user]@gitlab.localhost): ["Email has already been taken"]

User side:
Could not authenticate you from Ldapmain because "Undefined method 'provider' for nil:nilclass".

This temp-email does not exist in the database, neither does the actual email of the account that I’m trying to use. Neither have “already been taken”. Where is this temp email even coming from?
(I checked the Postgres database manually, but the user/email doesn’t exist in the GUI either)

I’ve tried with multiple test accounts now, they all fail the same way. Note that these test accounts are basically secondary accounts for users - BUT they have their own email address and username.

Has anyone seen anything like this before? Or any tips for debugging? There’s no more info that I can find in the logs.

Looks like GitLab isn’t able to get the email from the user.
Maybe some manual mapping might help…

Could you elaborate on what you mean by “manual mapping”? I’ve confirmed the email field I’ve configured in gitlab.rb exists in the account’s LDAP record.

That’s what I meant. I also don’t really know how to do it, I just came across it while scrolling through the docs trying to debug my issue.

‘attribute:’ setting of gitlab.rb is no problem?

  username: ['sAMAccountName']
  email:    ['mail']

If by “no problem”, you mean that isn’t an issue - yes all attribute fields are set in gitlab.rb, and the fields they are set to exist in the LDAP record.