Authentication Failed for user logging into D2

Lugaan · 2023-10-24T06:31:04+00:00

There was an error rendering this rich post.

Hi all,

After performing an upgrade of Documentum, migrated the db, ldap and .cnt files over. However I am still facing this issue whereby previously the user is able to login but now they can't.

This is the error that I am currently facing. Please do response if anyone knows the solutions for this.

Thank you in advance.

Find more posts tagged with

Documentum

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

Hicham Bahi

How is the user being authenticated ? inline password ? unix ? LDAP ?

If inline, I've seen cases where we had to reset all inline passwords (e.g. migration from Solaris to Linux). You can turn on trace_authentication to find out what's going on:

execute set_options with option='trace_authentication', "value"=true

Once enabled, try to login and look into the main docbase log file. Don't forget to disable tracing when done:

execute set_options with option='trace_authentication', "value"=false

Lugaan

https://forums.opentext.com/forums/developer/discussion/comment/967269#Comment_967269

The user is being authenticated via LDAP.

Lugaan

Hi quick question,

Is it because i didnt copy these files over from old PROD to the new UAT?

please do let me know.

Thank you in advance.

Hicham Bahi

No these are just output/trace files. I gave you a suggestion to trace the authentication. Did you do it?

Lugaan

Hi,

Sorry I havent done it, not sure where to run the command.

Please let me know.

Thanks.

Hicham Bahi

It's a DQL command. You can run it in DA DQL Editor, idql or iapi (prefix command with ?,c, for the latter) or any other tool that understands DQL (e.g. dqMan).

Lugaan

I am getting this, but not sure how to identify.

Hicham Bahi

It seems like the Content Server is not able to perform the bind. Perhaps because if invalid credentials. Try to enter the password again in your LDAP configuration object via Documentum Administration. This should regenerate the .cnt file.

Lugaan

is it the binding password?

Hicham Bahi

Yes. And obviously you also need to set the other mandatory information. (port / binding name).

Lugaan

I did all that, set the binding password. However only 1 .cnt file is new and the users is enable to login :(

Please do advice. Thank you.

Lugaan

https://forums.opentext.com/forums/developer/discussion/comment/967289#Comment_967289

I did all that, set the binding password. However only 1 .cnt file is new and the users is unable to login :(

Please do advice. Thank you.

Hicham Bahi

What do you mean only 1 .cnt is new? How many did you expect? Do you connect to several directories. You need to provide more information if you want people to help you.

Lugaan

https://forums.opentext.com/forums/developer/discussion/comment/967300#Comment_967300

So initially when I did the migration of Repository the .cnt files needed to be copied over. I had 9 files of .cnt. However, when I set all the information above and sync the server and check the dba\config folder there is only 1 .cnt is new (meaning today's date).

Hicham Bahi

You may want to remove the old files just for clarity. Furthermore, the logs show that the LDAP bind fails and that the Content Server then attempts to bind to the failover directory. So I assume that you have two dm_ldap_config objects in the repository. You also may want to check that network connectivity between the Content Server and the directory server is fine. It also suggest that you open a ticket with OT support.

Also, in the future it would be a good idea to include information such as Content Server platform/version and directory server you are using.

Lugaan

Alrighty, thank you so much. I am using 23.2 for documentum server and Microsoft Active Directory.

Lugaan

Hi,

Found what was causing the issue. In 23.2 LDAP is not supported anymore as it has deprecated.

So we would have to use OTDS to authenticate the users.

Hicham Bahi

That is correct but deprecated means that customers have to plan to migrate to OTDS, but it should still work. The trace clearly shows that the Documentum Server is attemtping to connect to the directory via LDAP.

bharath_ot1

Has any one integrated Documentum with OTDS already? we are getting error at this step
append,c,l,app_server_name, bad attribute error in API

Hicham Bahi

This is a different question so please make a separate post.