Integrating Aria Operations for Logs in Aria Operations using an Active Directory AD account fails with invalid credential
book
Article ID: 378246
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Integrating Aria Operations for Logs adapter in Aria Operations is successful when using the local admin account.
Integrating using an AD account fails with invalid credentials error bad username or password.
Even though you can successfully login directly to Aria Operations for Logs with the same AD account details.
The Aria Operations for Logs runtime.log may contain the following error when attempting to validate the credentials.
ValidationFailure{failureMessage='size must be between 5 and 100', violationPath='class com.vmware.ops.api.model.auth.UsernamePassword; Property: password'}
The Aria Operations for Logs ui_runtime.log may contain:
[2024-05-28 09:53:30.595+0000] ["https-openssl-apr-443-exec-5"/XX.XX.XX.XXX INFO] [com.vmware.loginsight.web.actions.misc.LoggerActionBean] [Submit form response {"succ":false,"validationErrors":[{"message": "Unable to validate Active Directory credentials. Please check your Active Directory DNS name, port, and SSL settings as well as your username and password.","detailMessage":"AuthenticationException: Invalid or untrusted domain 'XXX.XXX.XXX'.. See logs for details","fieldName":"adVerification","fieldNameStripped":"adVerification","fieldVal":null}],"errMsg":"Validation failed"}]
The AD account is created with uppercase USERNAME as the User Principal Name (UPN) and lowercase username as the 'Username'
AD authentication will accept the username in any format and does not differentiate between uppercase or lowercase
But the Aria Operations for Logs management pack integration in Aria Operations is expecting whatever is configured as the UPN in AD to be used for the integration.
Resolution
Configure the Operations for Logs management pack in Aria Operations using the UPN of the AD account.