LDAP authentication Error

Hi Team, I am trying connect the LDAP Microsoft ACtive Directory services to set up Single sign on. I am able to connect LDAP server by creating data source. I am created a base view with Objectclass->User->userprincipalname Got a error java.security.PrivilegedActionException Could you please help to connect LDAP for authentication trace name = user_0 database = db_ldap startTime = Wed Oct 9 22:14:45 373 CEST 2019 endTime = Wed Oct 9 22:14:45 400 CEST 2019 responseTime = - numRows = 0 state = ERROR completed = false fields = [userprincipalname] search conditions = [] filter conditions = [] ordered = false numOfFilteredTuples = 0 numOfDuplicatedTuples = 0 numOfSwappedTuples = 0 swapping = false memoryLimitReached = false LDAP WRAPPER ( name = user_0 database = db_ldap startTime = Wed Oct 9 22:14:45 374 CEST 2019 endTime = Wed Oct 9 22:14:45 399 CEST 2019 responseTime = - numRows = 0 state = ERROR completed = false searchConditions = [] orderByFields = [] projectedFields = [userprincipalname] additionalSubPlans = 0 additionalErroneousSubPlans = 0 LDAP ROUTE ( name = user_0#0 datasource = sit_ldap datasource database = db_ldap startTime = Wed Oct 9 22:14:45 374 CEST 2019 endTime = Wed Oct 9 22:14:45 399 CEST 2019 responseTime = - numRows = 0 state = ERROR completed = false exception = java.security.PrivilegedActionException LDAP URI = ldap://dev.ttt.com:389/ use paging = false userName = svc@dev.ttt.com filter = (objectClass=user) recursive search = true projected attributes = [userprincipalname] connectionTime = 24 cachedStatus = false
user
09-10-2019 16:25:18 -0400

1 Answer

Hi, The java.security.PrivilegedActionException error is very generic and happens due to different reasons. In order to know the specific root cause for the error, I would check the **vdp.log** file found under the **''<DENODO_HOME>\logs\vdp''** folder which contains the **LDAP error code**. **For instance:** If the error shows **data code is 0** then the problem might be due to the incorrect Distinguished Name(DN). In that case, I would reconfigure the Distinguished Name such that the LDAP user is located properly. You can have a look at [LDAP authentication best practices](https://community.denodo.com/kb/view/document/LDAP%20authentication%20best%20practices?category=Security) Knowlegde Base Article for more information. Hope this helps!
Denodo Team
10-10-2019 07:14:19 -0400
You must sign in to add an answer. If you do not have an account, you can register here