LDAP Validation Does Not Allow Log In To Documaker Studio (Doc ID 2253051.1)

Last updated on AUGUST 14, 2017

Applies to:

Oracle Documaker - Version 11.5 and later
Information in this document applies to any platform.

Symptoms

On : 11.5 version, Documaker Studio. When trying to integrate LDAP Validation to Documaker Studio Login Process, although Active Directory is retrieving the Groups, logging in to Documaker Studio isn't occurring and DM Studio closes the workspace.

1. Customer created a new Active Directory and assigned individual IDs to the group (AD Group : DDPDOCUADMIN)

2. Created a Group in USERINFO with the same name as that Active Directory and made our IDs report to DDPDOCUADMIN

3. Below are the sample options in the INI File.

 

< Environment >

LDAP_Enabled = Yes

 

< LDAP >

ldap.host=###.##.##.##

ldap.port=389

ldap.timeout=10000

ldap.search.scope=sub

ldap.search.level=1

ldap.uid=DDPDOCUSA

ldap.pwd=7DnZeYhg

ldap.authentication.mode=simple

ldap.domain=dmsa.com

ldap.objects.search.string=cn=?

ldap.object.attributes=ddpdocuadmin

ldap.match.attributes=cn*

ldap.debug=yes

ldap.dn.identifier=cn

ldap.deref.link=No

 

 


EXPECTED BEHAVIOR

It is expected that LDAP will return a list of Groups that the user belongs to. One of those groups would be the DDPDOCUADMIN group which is correctly defined as a user in Documaker Studio.

The user logging in should be granted the Documaker Studio rights that are assigned to the DDPDOCUADMIN user id in Documaker Studio.

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms