Index

Managed systems

Description

Once the server plugins and loaded into Soffid, agents can be configured in order to synchronize repository information.

Addons installation 

In order to configure a new agent, before you must downloaded and installed the connector whom includes this agent.

You could see the complete list of Synchronization Server Connectors in the following link: 3. Synchronization Server Connectors

Configuration

To create or update an agent, you may follow the next configuration data.

Not all the agents have all the configuration implemented, some agent only have some features available.

Basics

Generic parameters

Each agent will have the following parameters:

Custom attributes

The other attributes depend on the used plugin. See Agents Guide to get details about specific plugin parameters.

Synchronization buttons

At the upper right side of the page, you will find three icons. This icons allows administrator to enforce synchronization of users, , roles,  and groups, . If you press on them, a set of tasks will be scheduled to synchronize all of them.

It is important to clearly specify the groups and the users type that should be spread to the managed system. Any user that does not belong to these groups or user types will be automatically deleted or disabled from the managed system. As an exception, if no group is entered, all groups will be spread.

Regarding the account names to be used in the managed system, the users domain must be specified too. The users domain defines the rule by which the account name is generated based on the user name and its attributes. If the account name is the same as the user name (as it is normally the case), the “Default user domain” should be used.

Regarding the password domain, the user will share the same password for all the managed systems with the same password domain. There is “Default password domain” that will share the passwords used on Soffid console.

On the right hand side of the agent code there are two icons that permit spreading all users or roles to the managed system.

Attribute Mapping

Soffid administrator have the chance to easily customize attribute mappings without having to code it using Java.

When a agent allows this kind of customization, a new tab named "Attribute mapping" will appear. On this tab, the user can make either inbound or outbound attribute mappings. The left hand side attributes are managed system attributes, so they are agent dependent. The right side attributes are Soffid attributes and must be selected from the list below.

When the mapping is bidirectional, both sides of the mapping must be naming a single account, but when the mapping is one way, the source attribute can be replaced with a bean Shell expression. 

Properties

Some agents require to configure some custom attributes in this properties section.

You could see these attributes in the "Properties" section of each single page

Attributes

System attributes

A configuration agent must define objects types that can be created on it. Each object mapping defines an agent object name and a bound Soffid object type. For each mapped object, a list of attributes will be displayed. At the left column the system's attribute name will be displayed, and at the rightmost column, the Soffid's attribute name will be shown.

Directions

At the center column, an arrow will show the direction the information flows. When the information flows from the system (left), to Soffid (right), the left column name can be replaced by a bean shell expression. This expression will be evaluated on the system object prior to uploading it to Soffid.

When the information flows from Soffid (right) to the managed system (left), the right column can contain a bean shell expression that will be evaluated prior to provisioning the user. Here are some examples:

Soffid attributes

List of Soffid attributes are described below

• User Object

• Account Object
• Group Object
• Role Object
• Grant Object
• Maillist Object
• Membership Object

When evaluatting any expression, either the system or soffid attributes are available as script variables. More over, the following variables are available:

Load triggers

Account metadata

To proceed to it, click on to set a new metadata.

At this point, the following should be indicated:

1. Order: number that determines the order in which the custom object will appear.
2. Code: text used by the system to refer to the object.
3. Label: description understandable to the user.
4. Data type: at this point, the data type of this metadata must be selected. The data type includes the default ones as well as the custom objects that may have been created in the system.
5. Prevent duplicated values: if this flag is enabled, there can not be an identical duplicate metadata.
6. Multiple values: if this flag is enabled, the metadata may contain more than one value.
7. Size: set the max length.

Once completed, click on to save data.

If the created metadata should be deleted, click on , located on the right of the created metadata, and then on to save data.

Now, once configured the account metadata in the corresponding agent, access the accounts screen, select one of the system to which that agent points and go to "accounts" tab. There it is possible to see that the metadata are sorted as was indicated in the agent.

It can also be checked on the "user" screen, by selecting a user and accessing the "Accounts" tab

Then, click on  located to the right of the account pointed to by the agent in which the metadata were defined.

A window opens and shows the account metadata, sorted how they were set in the agent.

Scripting

In the agents configuration it may be possible use scripting to include logic in the attribute mappings and in the trigger scripts.

In the attribute mapping, if you use a script in one side, it is mandatory a single direction to the other side:

• System attribute <= script
• script => Soffid attribute

Below a easy script to send a full name to the system:

system attribute <= return firstName + lastName;

Below a more complex script to create a main domain if it doesn't exist in Soffid:

String mailDomain = null;
if (email != void && email != null && email.contains("@")) {
    String[] mailTokens = email.split("@");
    mailDomain = mailTokens[1];
}
com.soffid.iam.service.MailListsService service = com.soffid.iam.ServiceLocator.instance().getMailListsService();
com.soffid.iam.api.MailDomain domain = service.findMailDomainByName(mailDomain);
if (domain==null) {
    domain = new com.soffid.iam.api.MailDomain();
    domain.setCode(mailDomain);
    domain.setDescription(mailDomain);
    domain.setObsolete(new Boolean(false));
    domain = service.create(domain);
}
return mailDomain;

=> mailDomain

More information

Password synchronization

The passwords a user have on an agent will be synchronized with any other "single user account" the user has on this agent. Shared accounts will never get its password synchronized.

Password in an agent will be also synchronized with any other account the user has on other agents that are sharing the same password domain.

The password change can be produced by an operator using Soffid console, the user itself using Soffid Self Service portal or a timed automatic task. Furthermore, some managed systems can forward their password to Soffid in order to get them synchronized. In order to accept this password changes coming from managed systems, the trusted passwords box must be checked for the source agent.

Mind that this is the flow for normal user passwords. Temporary passwords generated by Soffid console will only be sent to agents marked as trusted. Agents not checked as trusted will have a random new password instead. Later, when the user changes the password on Soffid or any trusted system, the new password will be notified to Soffid by the managed system, and every agent on the same password domain will actually get the new password.

Agents account management

The agent configuration sets the way accounts are created and disabled.

Whenever a user is modified, the following rules will be applied to check if the user should have or not an account on this agent:

1. The user type is check against valid user types
2. If there is a business unit or group bound to the agent, the user memership will be assessed.
3. If the role based box is checked, the system will verify if the user has any role or entitlment assigned on this agent.

If the user does not apply for any of the conditions, every account the user has at this agent will be changed to Disabled status.

If the user verifies avery one of the conditions, the user can have an account on this agent. Every account the uesr has at this agent will be changed to Enabled status.

Unless the "manual account creation" is checked, if the user can have an account on this agent, but it has no one, the account creation method will be invoked. To create it, Soffid will search for the user domain bound to this agent and will follow its configuration. If the user domain is configured with a script, this script will be executed and the result value will be accepted as the new account name. Mind that if the script returns a null value, no account can be created.

If the returning value from the script clashes with an existing account, the existing account will remain unchanged, unless the existing account is marked as a unmanaged account. In such a case, the account will be changed from unmanaged state to single user.