No logon to directory after OneView 5.5 upgrade

[Frank_ltnds]

Hello all,

I just had an annoying problem after upgrading my OneView appliance from version 5.4 to 5.5. Upgrade was successful, but afterwards I was unable to log on to appliance with any ActiveDirectory user account. Logon with local administrator works. All directory settings seem correct, I tested resetting the password of directory service account, but same result. I can browse the directory from users and groups settings, so there is obviously no connection problem between OneView and ActiveDirectory. But still no logon possible.

I finally had to restore my appliance to previous version (5.4) by VMware snapshot. No problems with OneView 5.4., logon works perfectly. Has anyone made a similar experience with 5.5?

Thanks a lot.

Frank

[ChrisLynch]

This is not expected, so please open a support case.  

[techguy52]

I just upgraded my lab OneView appliance from 5.4. to 5.5 this morning and I did not have that issue. I can still login with my AD account.

-Skip

[Frank_ltnds]

Ok, thank you. Important information that it generally works. I will retry updating and then do some more testing. Unfortunately I have no lab environment...

[inkostin]

Same problem.

[ChrisLynch]

@inkostin  please open a support case.  The forums here aren't meant to replace that process.  And this isn't a known issue.

[Frank_ltnds]

@ChrisLynch: I think that I cannot open a support case because I don't have OneView advanced licenses. Am I wrong?

[ChrisLynch]

If you are using the HPE OneView Standard license, then you need to ensure you have purchased the K6F98AAE SKU, which is HPE OneView Standard 1yr 9x5 Support and per OneView appliance.  Otherwise, yes, the HPE OneView Advanced license comes with 3 year 24x7 support by default.

[MarioE]

I have the same problem.
I have an AD group with 8 users. All users can log in, but one user can't.
Had to go back to version 5.4, where I don't have this problem.
HPE, you have a problem there, so please react, don't wait for customer cases!

[inkostin]

I created ticket to support.

The problem not solved.

[PriitP]

We have login problems with users, who's First or Last name (not the AD username) has non English alphabet letters. Users, who's First and Last name in AD has only English characters, can successfully log in to OV 5.5 Needless to say, that on OV 5.4 this problem didn't exsist.

Rgds

Priit

[MarioE]

Hello PriitP

Thanks for your comment.

My first thought was also that it is such a problem, because the user, who can't log in anymore, has an "ü" in his name.
His AD name, however, does not have a "ü", so I did not think that this could be the cause.
I had to get back to version 5.4 quickly and could not do any deeper testing.

[Frank_ltnds]

@PriitP: Thank you very much. I cannot test this immediately because we already reverted to OV 5.4, but I can confirm that all accouts I used for testing had different logon names, but all of them had an "ö" in their last name, because of my own name.

[MarioE]

In our Active Directory the user has the following names:
Display name: <Name with ü>
Second name: <Name with u>
distinguishedName: CN=<Name with ü>

[Daniel-L]

Hello MarioE,

I can confirm the issue with the German "Umlaut".

If Last name / Display name contains an "umlaut" (ü, ö, ä...) users can't login.

All other users in the same group can login successfully.

Will open a case rightaway.

[ChrisLynch · Accepted solution]

Regarding non-English characters in user names, this is a bug and will be fixed in our next release we have planned.

[Frank_ltnds]

@ChrisLynch: Perfect, very good news, thank you for this information.