Add support for Web Services Option. See INTIDBCHRS:Web Services Option for details, along with SDK attached to INTIDBCHRS:v7.7 Documentation.

Hi Peter,

In section 8.1.3 Identity Broker Adpaters configuration for the Empower Person Adapter of the ACG CEO Technical Design document.

The first three transformation type are "Relation.Group" but the mapping configuration information is using TargetColumn and SourceColumn instead of GroupTarget and RelationReference.

Based on my understanding I assume this assume TargeteColumn should be GroupTarget and the SourceColumn should be RelationReference.

Please clarify.

The tooltips for Identity Broker for chris21 are not particularly helpful. For example: The "Username" text box has a hint similar to - "The chris21 username".

Please update all hints that are not useful.

Thanks.

A Chris21 Connector without Advanced settings will have a List Request Value set to All. A Chris21 Connector without Advanced settings will have a List Request Values set to Default.

The default should be consistent between both Advanced non-advanced settings.

Placed Filter

posend:GE:{DATETODAY}:or, posend:EQ:

into filter.
XML shows correct settings, but UI converts

into current date.

eg today this shows:

posend:GE:2013-03-07:or, posend:EQ:

GTR Filters are not displayed on Connector. One must disable connector, then go into configuration to see configuration.

The chris21 connector will always re-retrieve an updated entity from the repository for attachment handling. The retrieval should be moved entirely within the scope of the attachment handling section to avoid this needless performance hit.

Could someone please tell me, or point me towards, the documentation which tells me the exact requirements for the IdB service account.

Executing an MA attached to a disabled adapter will import the last processed entity count
See screenshot attached

The LDAP engine is unable to process multiple modify requests to a single entity if they occur on the same page. It is simple enough to make the request handler map entity IDs to a list of requests rather than just a single request, but the real problem is merging the changes on the change report (which deals with IConnectorEntitys). Perhaps the effects of the requests should be merged at a level higher than this.

There are currently no known systems that will send requests like this, so this is not urgent.