Invalid credentials

Michal.Kopecny,

You may want to verify that it is allowing complex passwords. You can do so by;

By setting that you get the ability to then require/allow the following

English uppercase characters (A through Z).

English lowercase characters (a through z).

Base-10 digits (0 through 9).

Non-alphanumeric (for example, !, $, #, %). extended ASCII, symbolic, or linguistic characters.

Let me know if this helps.

I'm having a similar issue, but I did it as Group memberships.  None of the logins work, but it works when I do the test.  I've checked and rechecked all the settings and gone over the (very light) instructions.

Hi all,

I have installed a new Dell EMC OpenManage enterprise, but failed to login via Web console. I double confirmed that the username "admin" and passcode is correct.

why?

B.R

AW

I even could not logon OME Enterprise default web portal with "admin" after deployment.

i also set this up with group membership, and it only works when i use domain\username as username.

i see no option for changing this.

Hi Chris,

the problem is not in the password but the login name itself.. If I create a user without the dot character in the login name in the same domain and the same group, I can log in just fine.

Thanks for looking into this matter.

Hi folks,

I've been off digging into this.  Short story: yep, bug.  Dots are a problem in user name.  I've notified the team to address.

Thanks for the post and sorry for the inconvenience on this one.

Regards,

Rob

Thanks Marc, sending along...

Regards,

Rob

Hi AW,

Can you confirm you went to the Text User Interface to accept the EULA and create your initial credentials for the appliance?

Thanks much,

Rob

Hey Michal, back this original post of yours.

Just to get a bit more info, is the issue:

1. You can use user names with dots *if* they are in AD groups.

2. But cannot use names with dots if they are local.

Looking at trying to repro and the local names with dots are not accepted, but if you import and use a name that is in a group and it has dots, it looks to work.

Are you seeing the same?

Rob

 I am experiencing the same thing. Have tried every which way to import an AD group to allow login. The Test connection says everything is working, when when I attempt to login with AD credentials, I am told it has failed. 

I can confirm in this instance that the username being used as no non-alphahnumeric characters in the samaccountname attribute, and the the group being used also makes no use of non-alphanumerics. I've tried:

• username@domain.com
• domain.com\username
• NetBIOSLabel\username
• username

Have also attempted to use as the username the following attributes with their values:

• samaccountname
• cn
• userprincipalname
• name

None of these variations resulted in a successful login using AD.

ok, thanks bcshort for this extra detail.  I'm passing to the team to help with the re-pro.

Thx

Rob

Has anyone successfully set up AD authentication?
I have successfuly set up the directory service AD type (test successful).
I then used "Import Directory Users" and browse to find the group to add. It was also successful with the group showing up in users "table" with enabled with role=administrator. BTW, the group should be listed in a different menu, and not under Users. That's confusing.

I tried logging in via the following method and they've all failed. The audit log also is not helpful - CUSR1219 - Unable to log in because the provided username or credentials are invalid. Not sure whether it was wrong user name, wrong user in the group, wrong password, etc.

These are the formats for the names with no success:
- domain.local\username
- domain\username
- username@domain.local
- username

Thanks for the post.  We are looking at some issues where usernames with underscores and dots are not working.

And a few folks have found a workaround by doing this:

- Under Application | Directory Services, when you click Add, choose Manual and enter IP rather than FQDN

Not sure if this is relevant to you but thought I'd toss it out there.

Regards,

Rob