Error user with this e mail already exist

Importing user from LDAP to RH-SSO fails with error «email already exists»

Environment

• Red Hat Single Sign-On (RH-SSO)
  • 7
• Lightweight Directory Access Protocol (LDAP) or Active Directory Lightweight Directory Service (AD)

Issue

Could not able to import users

Exception thrown in the logs:

Resolution

This error occurs when single e-mail id is mapped with multiple users.

You can make sure no 2 uses have the same email address, or use one of 2 workarounds:

1. Delete e-mail mapper
   1. Login into RH-SSO console
   2. Select the appropriate realm
   3. Click on User Federation and Click on appropriate provider
   4. Go to Mappers tab, click on email attribute mapper and click on the delete symbol
      
2. Turning on «Duplicate emails» in the Login tab
   1. Login into RH-SSO console
   2. Select the appropriate realm
   3. Go to Login tab and turn off Login with email settings. Then, Duplicate emails appears.
   4. Turn on Duplicate emails and save it.
      

Root Cause

RH-SSO does not allow multiple user to have same email-id when Login with email is enabled, which is the default.

• Product(s)
• Red Hat Single Sign-On

• Component
• jbossas

• Category
• Troubleshoot

• Tags
• active_directory
• email
• jboss_security
• ldap
• security

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Источник

Bitrix24Care

Here are some problems that you may face when logging in and instructions on solving these problems. First you need to log in to your Bitrix24 account.

«Incorrect login or password» error

If it doesn’t work, make sure that there are no typos in your login.

«We cannot find this user» error

This error may occur if you’ve already logged in to your Bitrix24 Network profile that is not connected with the selected Bitrix24 account.

Make sure that you are using the correct login information — it can be another email, mobile phone, or social network. If necessary, you can add this user to the account by sending an invitation.

«Failed to find user with this email» error

The error occurs if this email is not registered in Bitrix24. Check the specified login. It is possible that it is another email, mobile phone or social network.

«User may have been dismissed» error

The error occurs when this user was dismissed and he/she is trying to log in to. After an employee is fired, access to Bitrix24 is denied to him/her. Check whether the user is logging in to the correct account.

When registering using social services, you authorize in Bitrix24 using the data from these social networks. You can connect your email to your account and log in using your username and password.

«A user with this email already exists» error message when trying to change your login in Bitrix24 Network profile

This error occurs if you are trying to connect an email account that is already registered in Bitrix24. In this case you can use another email or unlink the desired email from the account. To do this, go to the Bitrix24 Network profile by email you want to unlink and click Change in the email field. Specify a new email address and confirm it. You will be able to connect it to the account.

«Invalid checkword» error

If this error occurs when you change your password, it may be due to several reasons:

• You have sent several password recovery requests and followed an outdated checkbox. To successfully change your password, follow the link from the last email and set a new password for your account.
• The recovery link is valid for 60 minutes. Make sure it has not expired.
• There is already an active authorization in your browser for Bitrix24 Network profile, for which you do not need to restore the password. Use «Incognito» mode in your browser.

«A user with email address already exists» error message when inviting a new user

This error message means that there is a user with this email address specified as a Bitrix24 Network profile login or as a contact email address in his Bitrix24 profile or both. In this case, there is no way to invite a new user with this email. You need to either change email addresses of the existing user or invite a new user using the other email address.

I made a mistake in the email address when registering a new user and now this user cannot log in

You can dismiss the user with a mistake in the email address and invite or register this user again.

Invitations/password recovery emails are not delivered

If you use your own mail domain, whitelist no-reply@bitrix24.net email address.

I was invited to the account, but I can’t log in. What should I do?

Before logging in to the account, you need to register a login and set a password.

I’ve lost my phone and cannot log in as I don’t have a one time password

If you don’t, contact your administrator to disable two-step authentication.

Change the user email address for the dismissed user’s email address

Then the dismissed employee needs to log in to his/her Bitrix24 Network profile and change the login. You can read how to do that in the article: Change my Bitrix24 login or password.

If the administrator has access to this account or email, he/she can do that himself/herself.

After that, you can invite/register a new user with this email address.

Delete Bitrix24 account

You cannot delete Bitrix24 account as long as there is a Bitrix24 connection. As soon as your account is not linked to any Bitrix24, the deletion option will appear in the account menu.

Cookies: This website uses cookies for analytical and technical reasons. ‘Analytical Cookies’ are inserted by Google Analytics to help us understand which countries our visitors come from, which pages they visit and what actions they take on this site. ‘Strictly Necessary Cookies’, as the name implies, are a type of cookies that are required for proper functioning of certain features of this website, such as the ability to use live chat. Disabling these cookies will disable access to those features and degrade your website experience.

Cookies of both types can be enabled or disabled within this plugin.

Источник

Issues

Context Navigation

#19404 closed Bug (worksforme)

Updating User’s email in Admin fails if email already exists

Description

If you had two users with different email addresses, then changed email address of User #1 via the admin page by setting it to that of User #2, then you would get this error:

django/contrib/auth/hashers.py», line 135, in identify_hasher

if len(encoded) == 32 and ‘$’ not in encoded:

TypeError: object of type ‘NoneType’ has no len()

The above is a simple scenario just to create the error. In real life, with thousands of emails, one wouldn’t know if an email is duplicate or not.

An error message could be raised here instead of the above error message that is not that intuitive for the above case.

Change History (5)

I can’t reproduce this problem.

What’s especially weird is that the code you’re describing is about password hashing, which has nothing to do with the email address. This suggests that you’re doing something different out of the box that you’re not telling us about.

If you can provide more specific instructions about *exactly* what you’re doing (e.g., if you’re using a custom User model, if you’re using the admin interface, what python calls you’re making), feel free to reopen.

This appears to be a duplicate of #19349

What’s especially weird is that the code you’re describing is about password hashing, which has nothing to do with the email address. This suggests that you’re doing something different out of the box that you’re not telling us about.

If you can provide more specific instructions about *exactly* what you’re doing (e.g., if you’re using a custom User model, if you’re using the admin interface, what python calls you’re making), feel free to reopen.

More info

No custom user.
UserAdmin has been modified (reregistered) with the following to check for duplicate email address during creation and change.
UserCreateForm works as expected. However, UserChangeForm results in this issue. (Both forms inherit from Django and update the required fields.

Источник

«A user with this name already exists. Use a different name.» error in the Microsoft 365 portal

Problem

In Microsoft 365, you receive an error message that’s like the following in the Microsoft 365 portal:

A user with this name already exists. Use a different name.

Cause

This issue may occur if the user name is already used or if an existing email address that’s based on the user name already exists.

The licensing attempt will fail if the provisioning process determines that another object already has a user name or an email address that matches the user name that’s being created.

By default, when users are added or assigned an Exchange Online license, the users are provided with a primary SMTP address that’s based on their user name. And, users are provided with an email address that’s based on the Microsoft Online Direct Routing Domain (MODRD) such as, for example, contoso.onmicrosoft.com. Additionally, when a user name is changed, the primary SMTP address may also be changed. However, alternate addresses aren’t updated or removed.

Here are some example scenarios.

Scenario 1

A user is added who has a user name of john@contoso.com, the MODRD for the organization is contoso.onmicrosoft.com, and the user is assigned an Exchange Online License. In this scenario, the following email addresses are provided:

• The user is provided with a primary SMTP address that’s john@contoso.com.
• The user is provided with an alternate email address that’s john@contoso.onmicrosoft.com.

Scenario 2

A user is added who has a user name of john@contoso.onmicrosoft.com, the MODRD for the organization is contoso.onmicrosoft.com, and the user is assigned an Exchange Online License. In this scenario, the following email address is provided:

• The user is provided with a primary SMTP address that’s john@contoso.onmicrosoft.com.

Scenario 3

A user name is changed from john@contoso.com to johnsmith@contoso.com. In this scenario, the following events occur:

• The primary SMTP address, john@contoso.com, may be changed to johnsmith@contoso.com.
• The alternate email address, john@contoso.com, isn’t changed. Therefore, problems occur if you try to add john@contoso.com later.
• No alternate email address for johnsmith@contoso.onmicrosoft.com is created.

Solution

To fix this issue, do one or more of the following:

• When you add a user, use a different user name.
• When you add a user, find and change the existing user name so that you can use the user name with which you are experiencing the issue.
• When you add or assign a user to an Exchange Online license, find and change the existing email addresses that are based on the user name that you are trying to use.

To check whether an email address already exists, follow these steps:

Connect to Exchange Online by using remote PowerShell. For more info about how to do this, go to the following Microsoft website:

Run the following cmdlet:

«user name» is the user name with which you are experiencing the issue.

Based on the results that you receive after you run the cmdlet, update or delete the existing email address.

Источник

Error user with this email already exists

Delivery has failed to these recipients or distribution lists:

jbloggs
The recipient’s e-mail system can’t process this message at this time. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or provide the following diagnostic text to your system administrator.

Diagnostic information for administrators:

Generating server: mail01.theirdomain.com

However right now sending an email internallt to jbloggs@theirdomain.com appears to be working now. Previously I was getting an error saying a message bounce between two servers was happening.

I have three domains in one forest. I noticed that there was a complaint that the infrastructure master was on a gc for the root domain i have moved this now to an non gc server (windows 2003 sp2) but apart from this replication looks ok. in the domain i am having the account probelm there are 3 dcs.

Still if I open the account jbloggs and try to add jbloggs@theirdomain.com it says email address already exists.

I have spent the whole day at this now trying to figure it out 🙁

Источник

Here are some problems that you may face when logging in and instructions on solving these problems. First you need to log in to your Bitrix24 account.

Пожалуйста, прочтите мой код, мой вопрос со снимками экрана и вещи, которые я уже пробовал, относятся к моему коду.

Manager.py:

from django.contrib.auth.base_user import BaseUserManager
from django.utils.translation import ugettext_lazy as _

class CustomUserManager(BaseUserManager):

    def create_user(self, email, password, **extra_feilds):
        if not email:
            raise ValueError(_('The Email must be set'))
        email = self.normalize_email(email)
        user = self.model(email=email, **extra_feilds)
        user.set_password(password)
        user.save()
        return user

    def create_superuser(self, email, password, **extra_feilds):
        extra_feilds.setdefault('is_staff', True)
        extra_feilds.setdefault('is_superuser', True)
        extra_feilds.setdefault('is_active', True)

        if extra_feilds.get('is_staff') is not True:
            raise ValueError(_('Superuser must have is_staff = True'))
        if extra_feilds.get('is_superuser') is not True:
            raise ValueError(_('Superuser must have is_superuser=True'))
        return self.create_user(email, password, **extra_feilds)

Models.py:

from django.db import models
from django.contrib.auth.models import AbstractBaseUser, PermissionsMixin
from django.utils.translation import gettext_lazy as _
from .managers import CustomUserManager

class CustomUser(AbstractBaseUser, PermissionsMixin):
    email = models.EmailField(_('email address'), unique=True)
    first_name = models.CharField(max_length=40)
    last_name = models.CharField(max_length=40)
    
    USERNAME_FIELD = 'email'
    REQUIRED_FIELDS = []

    objects = CustomUserManager()

    def __str__(self):
        return self.email

Forms.py

from django.contrib.auth.forms import UserCreationForm, UserChangeForm
from .models import CustomUser, StripeConnectSetup
from django import forms

class CustomUserCreationForm(UserCreationForm):

    class Meta(UserCreationForm):
        model = CustomUser
        fields = ('email', 'first_name', 'last_name')

class CustomUserChangeForm(UserChangeForm):

    class Meta:
        model = CustomUser
        fields = ('email','first_name', 'last_name')

Views.py

from django.shortcuts import render, redirect
from .forms import CustomUserCreationForm, CustomUserChangeForm, StripeConnectSetupForm
from .models import CustomUser
from django.contrib.auth import login, logout
from django.contrib.auth.forms import AuthenticationForm

def update_user_view(request):
    obj = CustomUser.objects.get(email=request.user.email)
    data = {'email': obj.email, 'first_name': obj.first_name, 'last_name': obj.last_name}
    form = CustomUserChangeForm(initial=data)
    if request.method == 'POST':
        form = CustomUserChangeForm(request.POST, request.FILES)
        if form.is_valid():
            obj = CustomUser.objects.get(email=request.user.email)
            obj.email = form.cleaned_data['email']
            obj.first_name = form.cleaned_data['first_name']
            obj.last_name = form.cleaned_data['last_name']
            obj.save()
            return redirect('accounts:update_user')

    context = {
        'form': form
    }
    return render(request, 'accounts/update_user.html', context)

Update_user.html:

<h1>Update User Profile</h1>
<hr>
<form method = "POST" enctype = "multipart/form-data"> {% csrf_token %}
    {{form.as_p}}
    <button type = "submit" class = "btn btn-primary">Update</button>

</form>

Проблема:
при попытке обновить свою учетную запись, если я не хочу менять свой адрес электронной почты (только мое имя или фамилию), отображается ошибка «Пользовательский пользователь с этим адресом электронной почты уже существует»

Я искал много решений, и единственное, что показалось работающим, — это прохождение функции очистки в форме обновления, как показано ниже:

Forms.py

class CustomUserChangeForm(UserChangeForm):

    class Meta:
        model = CustomUser
        fields = ('email','first_name', 'last_name')
    def clean(self):
        pass

Это устраняет проблему и позволяет обновить свое имя или фамилию, не обновляя адрес электронной почты.

Однако это вызывает другую ошибку.
когда я пытаюсь изменить свой адрес электронной почты на другой адрес электронной почты, который уже существует в моей базе данных, вместо того, чтобы получить ошибку «Пользовательский пользователь с этим адресом электронной почты уже существует», вместо этого загружается этот экран

Ошибка, возникающая при исправлении чистой функции

Итак, вопрос в том, как мне остановить ошибку «Пользовательский пользователь с этим адресом электронной почты уже существует», когда я не обновляю свой адрес электронной почты, но разрешить ошибку, когда я меняю свой адрес электронной почты, и этот адрес электронной почты уже существует.