Identity Broker Forum
Welcome to the community forum for Identity Broker.
Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.

Database connector - SQL schema provider should return timestamp fields as binary, not timestamp
The schema provider for the database connector currently returns a timestamp for timestamp fields. It should instead return a binary.

long schema field uneditable after incorrect data format used for max value validator
I set up a "long" schema field, with a max range of "-50.3". An error appears on the connector screen:
Incorrect value max attribute in <Extended max="-50.3" xmlns="" />
This error also appears if I attempt to update the schema field with a full stack trace, and does not let me update the field definition.
As an improvement, the message should tell the user which field contains the wrong validator.

Once off timings are never cleared from the home page
Once off timings are never cleared from the list of recent connectors, even well after they are expired. Moreover, they appear as "Inactive" and at the top of the list. This could cause issues if you have several connectors that had been configured to run once at the expense of those that run more regularly.

CSV connector adds additional new line for each export
An additional new line is added for each exported entry.

Multivalue DN Generator unclear output
If the DN generator of the MultiValue DN Generator transformation doesn't contain a schema field DN component of the source, it will always return null.
Either the documentation needs to be updated to better describe this. Or a prerequisite needs to be added to this transformation, such that, that DN generator component is always in the transformation.
Additionally currently nothing is logged that would indicate that this is the reason null values are coming through on reflection.

Updating RDN component generator reverts Adapter DN
When an RDN component generator is updated, the Adapter DN generator is replaced with a CN=schemaKey component.

Unable to add adapter to group
When attempting to add an adapter to an adapter group, the following is logged
Collection was of a fixed size.
During initial development of Identity Broker, this appeared due to serialization settings; additionally adapters could be added to groups in the last set of regression tests - so the change must be very recent.

Import errored alert not cleared on connector deletion
The alert raised with the label:
An error occurred whilst performing the task Import All. Please refer to connector Talent2 Person Connector4.
Is not cleared when the connector is deleted.
Ensure other alerts relating to components are checked to ensure that they are cleared when the component is removed.

Add connector doesn't save XML configuration
On adding a connector, the XML configuration of the connector engine isn't refreshed/saved, meaning that if no other change is made to the connector engine, the connector will be lost.

Optionally log SQL requests made by Identity Broker.
Include the ability to log SQL calls made by Identity Broker, which can be turned on/off on the UI.
Customer support service by UserEcho