A CSV connector configured to import a binary value fails with:

Change detection engine import all items for connector CSV Connector Example failed with reason Line 1 column 1 value of 010011010110000101101110 is not valid. Duration: 00:00:00.1406250

This was tried with a byte value, byte array value, binary value and base64 encoded string; all resulting with a message similar to the one provided above.

• Either the validator should be updated to handle string values
• Or an intermediate step is included where the CSV connector tries to parse the values retrieved based on the field ValueType, before creating with the Validator
• Otherwise, a more descriptive exception should be provided denoting that this connector doesn't support that value type.

Hi Guys,

I've been experiencing issues with the PowerShell connector in reporting export errors back to the MA. I'm using a try catch arrangement - with $components.Failures.Push($entity) however this does not appear to succeed in returning an error to the MA.

Attached is my current export script for Adds (Note that the reporting lines are commented out at the moment).

The MA in use is of the new Extensible Connectivity V2.0 type. It occurs to me that this may be similar to the issues we used to have on the IDB MA's with export errors being squashed if the 'Merge pending exports...' flag was not set correctly. However this setting is not present on the new MA type.

Issue is with this page: https://unifysolutions.jira.com/wiki/display/IDB305/Adapter+Engine+configuration

Namely (as per the comment I added there)

1) The Composite Adapter Configuration should also have its attributes documented (AdapterID and AdapterName at the very least are valid and I believe required)
2) The Composite Adapter also takes an image as a child element, which is also required.

The Time Offset transformation is limited to offsetting a timestamp by 23hrs 59mins and 59secs.

In the case of TAFE I am wanting to transform a date by 14 days (336 hours) which doesn't appear possible. I've looked at the Business Day Transformation however it only sets a flag rather than transforming the actual date/time.

I have installed Identity Broker Service v4.0 RTM x64 and Web Service v4.0 RTM x64. I have configure the for use with IIS as per https://unifysolutions.jira.com/wiki/display/IDB40/Configuring+for+use+with+IIS. When I browse to "http://localhost:8008/" I receive an error to add defaultRedirect="mycustompage.htm to the web.config file. I have add the line to the web.cnofig, run a IISRESET.

When I browse to "http://localhost:8008/" I receive the following error:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. Detailed Error Information
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error Configuration file is not well-formed XML
Config File \\?\D:\Program Files\UNIFY Solutions\Identity Broker\StandaloneWeb\web.config
Requested URL http://localhost:8008/
Physical Path
Logon Method Not yet determined
Logon User Not yet determined
Config Source
44:
45: <httpRuntime maxQueryStringLength="16384" />
46:
Links and More InformationThis error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »

Variations between Event/Identity Broker configurations being deployed between one environment and the next (e.g. DEV=>UAT=>PROD) are better identified programatically than with the human eye. A similar feature to that used for determinig FIM schema/policy variations during deployment such that the "changes only" migration can occur would be a useful feature for our Broker products as well. Initially a simple report on variations would be useful - and ultimately something akin to the "FIMDelta" feature demonstrated today by Carol might allow selective adds/updates/deletes to be driven via a UI tool.

Currently most service accounts won't have permission to write to the log/extensibility files. I know this is because we're not using AppData and we've discussed changing it, but we might need something more immediate for LITE.

The pop up that appears when a log entry is clicked is too narrow.

It needs to be at least 3 times as big (on my screen). Or maybe a percentage width? Also see if there is a way to stop the top getting set to a negative number.

Upgrade the configuration engine to allow for:

• Individual configurations to be retrieved/applied.
• Make configuration engine use application storage;
• Migration code from install directory to application storage;
• All configuration files to be retrieved/applied - possibly zip them up?
• Endpoint methods to allow for UI integration;
• UI for configuring settings and retrieving/applying configuration.

See https://unifysolutions.jira.com/wiki/pages/viewpage.action?pageId=41320640 for further details.

Trying to do a full import on multiple SAP connectors in 64bit mode..

Change detection engine import all items for connector sapOrgUnit failed with reason The request channel timed out while waiting for a reply after 00:00:59.9960936. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.. Duration: 00:01:00.1614898