{"id":3948,"date":"2014-10-17T02:11:00","date_gmt":"2014-10-17T00:11:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-project-ntlm-sso-with-d2-31-sp1-d2fs-d2lockbox\/"},"modified":"2014-10-17T02:11:00","modified_gmt":"2014-10-17T00:11:00","slug":"documentum-upgrade-project-ntlm-sso-with-d2-31-sp1-d2fs-d2lockbox","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-upgrade-project-ntlm-sso-with-d2-31-sp1-d2fs-d2lockbox\/","title":{"rendered":"Documentum upgrade project: Configuring NTLM SSO for D2 3.1 SP1"},"content":{"rendered":"

\"\"<\/p>\n

The Documentum D2 3.1 SP1 release is kind of a mix between D2 4.1 APIs (using D2FS in backend) and D2 3.1 front-end. It needs SSO to be fully implemented and the configuration has to be applied for 3.1 as well as for D2FS. For D2FS, the same configuration applies whether you are using the NT Lan Manager (NTLM) or Kerberos authentication.<\/p>\n

If you want to implement Kerberos Single Sign On instead of NTLM, have a look at this blog post: https:\/\/www.dbi-services.com\/index.php\/blog\/entry\/kerberos-sso-with-documentum-d2-31-sp1<\/a><\/p>\n

1. NTLM configuration for D2 3.1 SP1<\/h3>\n

The D2 3.1 documentation explains how to configure NTLM for D2 3.1 SP1.
\nReferring to the D2 3.1 installation guide, you can see the following:<\/p>\n

Locate the file \u00ab shiro.ini \u00bb used by D2 applications and add the following lines:<\/p>\n

[main]<\/span><\/span><\/p>\n

D2-NTLM=<\/span><\/span><\/span><\/span><\/strong>eu.c6.d2.web.filters.authc.D2NtlmHttpAuthenticationFilter<\/strong><\/span><\/span><\/span><\/strong><\/p>\n

D2-NTLM.domainController=<\/span><\/span><\/span><\/span><\/strong><<\/strong><\/span><\/span><\/span><\/strong><\/strong><\/span><\/span><\/span><\/strong>domain controller> <\/strong><\/span><\/span><\/span><\/strong><\/p>\n

D2-NTLM.domainName=<\/span><\/span><\/span><\/span><<\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span><\/span>domain name><\/span><\/span><\/span><\/strong><\/p>\n

D2-NTLM.domainUser=<\/span><\/span><\/span><\/span><\/strong><<\/strong><\/span><\/span><\/span><\/strong>domain user to authentify><\/strong><\/span><\/span><\/span><\/strong><\/p>\n

D2-NTLM.domainPassword=<\/span><\/span><\/span><\/span><\/strong><<\/strong><\/span><\/span><\/span><\/strong><\/strong><\/span><\/span><\/span><\/strong><\/strong><\/span><\/span><\/span><\/strong>user’s passwords> <\/strong><\/span><\/span><\/span><\/strong><\/p>\n

D2-NTLM.docbases=<\/span><\/span><\/span><\/span><\/strong><<\/strong><\/span><\/span><\/span><\/strong><\/strong><\/span><\/span><\/span><\/strong><\/strong><\/span><\/span><\/span><\/strong>docbase1,superUser1,password1,domain1|docbase2,…> <\/strong><\/span><\/span><\/span><\/strong><\/p>\n

[urls] <\/span><\/span><\/span><\/span><\/strong><\/p>\n

\/** = <\/span><\/span><\/span><\/span><\/strong>D2-NTLM <\/strong><\/span><\/span><\/span><\/strong><\/p>\n

 <\/p>\n

\u201cdocbaseX\u201d: corresponds to a docbase using NTLM
\n\u201cloginX\u201d: corresponds to a supersuser login of \u201cdocbaseX\u201d
\n\u201cpasswordX\u201d: corresponds to an encrypted password of the superuser of \u201cdocbaseX\u201d.<\/p>\n

In our case, the file is located in the following path: <Tomcat root>\/webapps\/D2-Client\/WEB-INF\/classes\/
\nAt first look, everything is there. However, some clarifications are very welcome.<\/p>\n

About Active directory connection:<\/p>\n