01-27-2014 09:14 AM
So I am still getting accustomed to the layout/configuration of OneView and while setting up the Active Directory integration, it doesn't appear to allow sAMAccountName as a attribute to use for login. It looks to only allow CN or UID. Is there any way to use sAMAccountName as an alternative? The security features of integrating the product with AD are great, but for us the inability to use sAMAccountName for login will be a pain.
01-27-2014 11:57 AM
I'm sorry Ryan, but HP OneView does not support UPN or samAccountName authentication today. We only support the Distinguished Name value of a user account when using Active Directory. Do know that we are always looking at ways to improve the product.