Kerberos Connector

Specify the details of the user principal and the default realm here. The sample provisioner file has the following custom configuration:

"customConfiguration" : "kadmin {
    cmd = '/usr/sbin/kadmin.local';
    user = '<KADMIN USERNAME>';
    default_realm = '<REALM, e.g. EXAMPLE.COM>'
}"

A complete custom configuration will look something like this:

"customConfiguration" : "kadmin {
    cmd = '/usr/sbin/kadmin.local';
    user = 'openidm/admin';
    default_realm = 'EXAMPLE.COM'
}"

Set the password for the user principal here. The sample provisioner has the following configuration:

"customSensitiveConfiguration" : "kadmin {password = '<KADMIN PASSWORD>'}"

Change this to reflect your user principal password, for example:

"customSensitiveConfiguration" : "kadmin {password = 'Passw0rd'}"

The host name or IP address of the SSH server on which the kadmin command is run.

The port number on which the SSH server listens.

Default: 22 (the default SSH port)

The username of the account that is used to connect to the SSH server.

The password of the account that is used to connect to the SSH server.

A string representing the remote SSH session prompt. This must be the exact prompt string, in the format username@target:, for example root@localhost:~$ .

If the prompt includes a trailing space, you must include the space in the value of this property.

Consider customizing your Linux prompt with the PS1 and PS2 variables, to set a safe prompt. For information about customizing promtps, see this article.

A string that shows the full path to the sudo command, for example /usr/bin/sudo.

If set to true (the default), the input command echo is disabled. If set to false, every character that is sent to the server is sent back to the client in the expect() call.

Sets the terminal type to use for the session. The list of supported types is determined by your Linux/UNIX system. For more information, see the terminfo manual page (man terminfo).

Default: vt102

If set to true, indicates that the default environment locale should be changed to the value of the locale property.

Default: false

Sets the locale for LC_ALL, LANG and LANGUAGE environment variables, if setLocale is set to true.

Default: en_US.utf8

Specifies the connection timeout to the remote server, in milliseconds.

Default: 5000

Specifies the timeout used by the expect() calls in scripts, in milliseconds.

Default: 5000

Sets the authentication type, either PASSWORD or PUBKEY. For more information, see "Configuring Authentication to the SSH Server".

Default: PASSWORD

If true, the connector throws an exception when the timeout is reached for an operation. Otherwise, the operation fails silently.

Default: true

The path to the Groovy scripts that will perform the ICF operations, relative to your installation directory. For the Kerberos connector, the scripts are bundled up in the connector JAR file, so this path is set to jar:file:connectors/kerberos-connector-1.5.20.8.jar!/script/kerberos/ in the sample connector configuration.

The directory in which the compiler should look for compiled classes. The default classpath, if not is specified, is install-dir/lib.

The script that is used for each ICF operation. Do not change these script names in the bundled Kerberos connector.

Provides simple authentication with two parameters, presumed to be a user name and password.

Creates an object and its uid.

Deletes an object, referenced by its uid.

Resolves an object by its username and returns the uid of the object.

Describes the object types, operations, and options that the connector supports.

Enables an application to run a script in the context of the connector. Any script that runs on the connector has the following characteristics:

Runs a script on the target resource that is managed by this connector.

Searches the target resource for all objects that match the specified object class and filter.

Polls the target resource for synchronization events, that is, native changes to objects on the target resource.

Tests the connector configuration. Testing a configuration checks all elements of the environment that are referred to by the configuration are available. For example, the connector might make a physical connection to a host that is specified in the configuration to verify that it exists and that the credentials that are specified in the configuration are valid.

This operation might need to connect to a resource, and, as such, might take some time. Do not invoke this operation too often, such as before every provisioning operation. The test operation is not intended to check that the connector is alive (that is, that its physical connection to the resource has not timed out).

You can invoke the test operation before a connector configuration has been validated.

Updates (modifies or replaces) objects on a target resource.