LDAP Configuration for ECC 6.0 ( ABAP Stack only)

[Former Member]

Hi,

Can any one guide me with the steps for the LDAP Configuration for ECC 6.0 ( Abap stack only).

Some of my observations are....

I can see the LDAP Support in the Installation master at the following path.

1. Additional Software Life cycle Tasks --> Application Server --> LDAP Support.

But the prerequisites for this task is given as "You must have extended the LDAP schema for the sap data types before.".

When i am goint thru service market place i came across the following note.

Note 888848 - Notes on schema enhancement with RSLDAPSCHEMAEXT.

Thanks,

Tanuj

[Former Member · Accepted solution]

Hi Tanuj,

please check <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/6c/eb0c3c30a85b4ee10000000a11402f/content.htm">here</a>.

Peter

--

Points always appreciated

[Former Member]

Dear All,

We are trying to configure the LDAP using with active directory .  In the

step of "Synchronization of SAP User Administration with LDAP

Directory"when executing the report"RSLDAPSYNC_USER" we are facing one

error.

Please find the trace file and error screenshot in the attachment.Please help us on

priority.

Please find the Trace log in the below:

RFC destination : LDAP_LDAPSE-01
Tracelevel      :      8,704
F5: Shutdown F6: Clear list F7: Dump status F8: Refresh list

[Wed Jun 26 11:15:38 2013]
Slot 0 (WIPROTECH): >>> ldap_initU(host="abg-mumabc-dc1.abgplanet.abg.com", port=389)

[Wed Jun 26 11:15:39 2013]
Slot 0 (WIPROTECH): <<< ldap_initU() == <NOT NULL> := connected
Slot 0 (WIPROTECH): >>> ldap_set_option(version=3)
Slot 0 (WIPROTECH): <<< ldap_set_option() == 0
Slot 0 (WIPROTECH): >>> ldap_simple_bind_sU(dn="poornataad", password: not initial)

[Wed Jun 26 11:15:40 2013]
Slot 0 (WIPROTECH): <<< ldap_simple_bind_sU() == 0 := success

[Wed Jun 26 11:15:43 2013]
>>>>Required attributes table
Line    0: "CREATETIMESTAMP" (length 15)
Line    1: "MODIFYTIMESTAMP" (length 15)
Line    2: "SAPUSERNAME" (length 11)
<<<<Required attributes table
Slot 0 (WIPROTECH): >>> ldap_search_sU(base="CN=poornataad,CN=Users,DN=abgplanet,DC=abg,DC=com", filter="(&(OBJECTCLASS=user)(SAPUSERNAME=*))", scope=2)
Slot 0 (WIPROTECH): <<< ldap_search_sU() == 91
>>> ldap_msgfree()
<<< ldap_msgfree()
Slot 0 (WIPROTECH): >>> ldap_unbind_s()
Slot 0 (WIPROTECH): <<< ldap_unbind_s() == 0

Please find the error screenshot in the below.

Regards,

Dilip Sampath.CH

+91-9619735957.

[Former Member]

Hi,

I think these are the steps to configure the LDAP with ABAP data source.

<b>1. Configure the LDAP connector

2. Configure connection data for the directory service

3. Define system user of the directory service</b>

4. Generate schema extension

5. Map SAP data fields to directory attributes

6. Set mapping indicators

7. Set synchronization indicators

I am able to connect to LDAP Server. I have completed the forst three steps. Please help me in completing the remaining steps.

I am using this document for reference. Please help me ...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/906061c5-176b-2910-5091-e23baa4e...

Thanks,

Tanuj

[Former Member]

Hi Tanju,

if you follow my previous posted link (and the link within it) you can read the following:

Procedure
       1.      Execute report RSLDAPSCHEMAEXT (for example, using transaction SE38).

The system displays the Generation of Schema Extensions screen.

       2.      Specify your directory service product using the possible inputs help.

       3.      Choose Execute.

This sould solve your problem, extending the LDAP-Schema.

Peter

--Points always appreciated

[Former Member]

Hi,

I executed the Report Already. It gave me a file Output. I did not know what to do with that ....Let me know how to proceed. I even executed th report RSLDAPSYNC_USER after that .. and no use..

Thanks,

Tanuj

[Former Member]

Hi Tanju,

if you follow my previous posted link (and the link within it) you can read the following:

Result

The system displays a list of attributes for schema extension that you can save in a local file on your front end. <b>Comment lines contained in the file explain how you can import the schema extension into your directory product</b> using the utilities of your directory service provider.

Peter

--

Points always appreciated