Configuring proxy transformations using dsconfig
Create and configure a proxy data transformation.
About this task
You can use PingDirectoryProxy to perform one of the following transformations:
-
Attribute mapping
-
Default value
-
DN mapping
-
Groovy scripted
-
Suppress attribute
-
Suppress entry
-
Simple-to-external bind
-
Third-party scripted
Steps
To create and configure a proxy transformation:
-
Run the
dsconfig
tool.Example:
$ bin/dsconfig
-
When prompted, enter the connection parameters to the server.
Connection parameters can include:
-
Host name
-
Connection method
-
Port
-
Bind distinguished name (DN)
-
Bind DN password
-
-
In the PingDirectoryProxy server main menu, enter the selection for
Proxy transformations
. -
In the
Proxy Transformation menu
, enter the selection forCreate a new proxy transformation
. -
Select the type of proxy transformation you want to create. Enter a name for the new transformation.
Example:
This example creates an attribute mapping transformation.
>>>> Enter a name for the Attribute Mapping Proxy Transformation that you want to create: userid-to-uid
-
To choose if the proxy transformation is enabled by default or not, select
true
orfalse
.Example:
Select a value for the 'enabled' property: 1) true 2) false ?) help c) cancel q) quit Enter choice [c]: 1
-
Enter the name of the client attribute that you want to remap to a target attribute.
This attribute must not be equal to the target attribute. Both the source and target attribute types must be defined in the local schema.
Example:
Enter a value for the 'source-attribute' property: userid
-
Enter the name of the target attribute to which the client attribute should be mapped.
Example:
Enter a value for the 'target-attribute' property: uid
Result:
The properties of your new proxy transformation are displayed.
-
Optional: To make any modifications, enter the selection for the desired property.
-
To finish the creation of the proxy transformation, enter
f
.Example:
Enter choice [b]: f
Next steps
The transformation must be assigned to a request processor. For information on creating and configuring request processors, see Configuring request processors.