Active Directory Error after Upgrade to
v3.0.3.4 SP2

 

Issue:

Due to
code the specification of the context path is written incorrectly in the
user-connectivity.properties file.

‘,dc=Domain,dc=com’

An
additional comma is entered in the description, causing the authorization
process to fail. You will be able to login using the AD credentials, but no
user will be able to see the batch classes of batch instances in the UI. 

Sample
Error:

3034 SP2 2013-09-09 12:04:54,252 ERROR http-8080-3
com.ephesoft.dcma.user.connectivity.impl.MSActiveDirectoryConnectivity –
,dc=Domain,dc=com: [LDAP: error code 34 – 0000208F: NameErr: DSID-031001BA,
problem 2006 (BAD_NAME), data 8350, best match of:

 ‘,dc=Domain,dc=com’

 ]

javax.naming.InvalidNameException: ,dc=hlf,dc=com: [LDAP: error code 34
– 0000208F: NameErr: DSID-031001BA, problem 2006 (BAD_NAME), data 8350, best
match of:

 ‘,dc=Domain,dc=com’

 ]; remaining name ‘,dc=Domain,dc=com’

 

Solution:

Download

http://www.ephesoft.com/Ephesoft_Product/Patches/30304SP2_AD_FIX.zip

Engineering has provided a hot-fix to address this issue, see
instructions below:

PROBLEM:

Customer is facing problem while connecting through Active
Directory after upgrading to Ephesoft product version 3.0.3.4SP2.

 

ANALYSIS :

From the shared artifacts we were able to dig into the root
cause of the problem. The problem occurs because of an extra character “,”
appended while creating the context path after fetching the value of properties
configured in user-connectivity.properties.

 

SOLUTION :

Please follow following steps to apply solution with respect
to v3.0.3.4SP2.

1.       Unzip the Attachment and Extract the file to temporary Location (Click
the download link above)
.

2.       Go to location [Ephesoft-Installation-Directory]/Application/WEB-INF/lib

3.       If the location contains any JAR file named
dcma-user-connectivity*.jar then take backup of existing jar file and then copy
the extracted jar file to this folder after deleting the existing jar file.

4.       Else directly copy the file in the attachment to this folder.

5.       Restart Ephesoft Server.

 

Problem will be rectified after applying the
solution.

 

Was this article helpful to you?

Walter Lee

Comments are closed.