LDAP settings transportation

[former_member610150]

Hi,

For LDAP we don't want to transport the LDAP server but we want to define it seperately in development and production. This because we don't want the production server to be available in our test system to avoid data from our test system can be send to our active directory production environment.

On the other hand, we would like to transport the LDAP mapping settings to avoid it can be modified in the production system (every change in the mapping settings can have a major effect).

The LDAP mappings seem to be linked to the LDAP server.

What's the best way to deal with this situation?

Regards, Jan

Edited by: J. Borgerink on Aug 29, 2011 3:45 PM

[former_member2987 · Accepted solution]

Jan if you are doing this in IDM, the easiest thing to do is define each LDAP instance as a separate repository, the same way you would do for SAP systems.

This lets you define customized connection parameters for each LDAP instance.

Hope this helps you out.

Matt

[former_member610150 · Accepted solution]

Matt,

Thank's for your answer. The problem is that we don't want to define the production repository in our development system. This would create the risk that there's a connection between SAP development and the Active Directory production system.

On the other hand we would like to transport the mappings for production from our development system to avoid they can be easily changed in the production system.

Define in Dev

Dev repository

Dev mappings

Prd mappings -> transport to Prd

Define in Prd

Prd repository

Regards, Jan

[former_member2987 · Accepted solution]

Then you would have to manually enter the values into IDM.

Matt