2013-01-10 09:43 AM
When discovering the storage within VSC after installing the application in the monitoring and host configuration panel, creating RBAC on the storage utilizing an AD user account, what is happening when that users authenticates and several "access denied" messages are splashing up on the display?
Contacted support and they collected the logs. Reviewed the logs and noticed that when an AD account authenticates <domain\username> is used, there is a problem of interpretation of a character (probably the "\") passed in the process. In troubleshooting, a local account on the storage is created and when authenticating with that account, all works as designed, no issues.
Our workaround is to create a local account on the storage, adding it to the group with specific roles, and it works as designed.
Another question I have is there a known BURT for this issue and if so, what is it and is it something that will be resolved in a future release of VSC?
2013-01-26 05:24 AM
Currently VSC doesn't support AD authentication to the storage system, and there is a BURT you can "watch" here: http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=619559
Additionally, in the interim, you can use the RBAC User Creator for Data ONTAP to create RBAC users directly on the storage controllers: https://communities.netapp.com/docs/DOC-19074/