Some users may have issues creating a community account. For more information, please click here.

Normalize fails with error - BDNA User Console logon not authorized as service administrator

Normalize fails with error - BDNA User Console logon not authorized as service administrator

Scenario:

Normalize fails with error - BDNA User Console logon not authorized as service administrator

All test connections to data sources and User Console test OK.

User Console Configuration wizard completes successfully.

Bdna.log :

ERROR System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: BDNA User Console logon not authorized as service administrator

Tomcat.log:

ERROR [UX] Login error, unexpected status code: 500
ERROR [org.pentaho.platform.plugin.services.security.userrole.CompositeUserRoleListService] User/Role List could not be obtained.
org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: DomainDnsZones.test.flexera.com:389 [Root exception is java.net.ConnectException: Connection refused: connect]]

Troubleshooting steps:

1) Verify if LDAP/AD server is actively refusing the access from User Console server.
2) Verify if there is a load balancer for LDAP/AD server

Possible solution:

Get the static IP address of the LDAP/AD server

Use one of the below two approaches:
a)Update system hosts file to add a static entry against LDAP/AD server host name, e.g. 192.168.1.1 test.flexera.com
or
b)Update LDAP/AD server name with the IP Address instead of the hostname in Data Platform configuration wizard then re-run Data Platform and User Console configuration wizard

If the above does not help resolve your issue, please log a new support case with us.

Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Mar 31, 2020 04:42 PM
Updated by:
 
Contributors