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.
Next run times don't look right for newly added connector schedules
It's ~9:30am and I just added and enabled an Import All and Import Changes schedule to a connector. The Import All I set to run at 12:55:57am, and the Import Changes every 1 minute. The following appeared, which doesn't look right - 1am isn't an hour away, and one minute is not 10 hours away:
Hi Adrian,
The scheduled times are displayed in the local time of the machine. In this case, the containers are running on UTC. So with the UTC time (at time of screenshot) being 11pm on 30 November, that looks accurate.
Created/Modified dates are not correct on the Remove Joins screen
On the Remove Joins screen the Created and Modified dates are both set to "00001-01-01 00:00:00Z" for Adapter entities:
This is not impacting me in any way and I'm just mentioning it for completeness.
This has been implemented and is available in the release of UNIFYConnect V6, which will be made available shortly.
Using Remove Joins (to view existing joins) generates DataTables Error (SocketException: the target machine active refused it)
The following UI error appears whenever I attempt to view joins via the 'Remove Joins' menu option on a Link in the Netwealth UNIFYConnect DEV instance:
I am using Chrome on the jumpbox VM, logged in with my UNIFY credentials. The error is not written to the UNIFYBroker log.
Fix deployed. Patch for reference (in Web/bin folder)
Improved UNIFYBroker/Plus log/UI messages (de/provisioning counts, incompletes, log message grouping)
UNIFYBroker/Plus would be easier to operate if the following logging and UI messages were added or made more clear:
* A log summary of the count of entities provisioned and deprovisioned by a locker synchronisation (this may already be there, but the terminology is "added" rather than "provisioned" - it would be nice if this was consistent with the UI and clearly delineated as being different to entities "added" to the adapter via reflection)
* An log explanation of the reason(s) why an entity's provision was Incomplete - i.e. which required fields are missing, or whatever else it was that caused it to be Incomplete.
* A way to identify all of the logging messages that are part of the same synchronization operation. In a busy log file it's hard to see the wood for the trees...
* Not to report un-joined and un-provisioned entities for a linker as Incomplete during Baseline Synchronization. The configuration clearly doesn't want these entities in the locker - but the yellow (i) box that appears seems to suggests that something may have gone wrong with them.
This has been improved with UNIFYConnect V6.
Link cannot synchronise a field change from Locker to Adapter
A Locker field value change is not appeared in an Adapter when Changes Synchronization runs. The same Locker/Adapter are able to provision objects just fine.
The UNIFYBroker/Plus config and logs are available in the Netwealth UNIFYConnect DEV instance; the Locker is "Employee", the Adapter is "SPOL Employee Suspensions", the Link is "Employees > SPOL Employee Suspensions". To trigger the change I make a change to a field value in the Employee connector source (an SFTP CSV file), run an Import All on the "ELMO Employees" connector, a Changes Synchronization on the "ELMO Employees > Employees" Link, then finally the Changes Synchronization on the "Employees > SPOL Suspended Employees" Link (which causes the following error to be written to the log):
After deleting a Link's Adapter it's not possible to edit that Link in the UI
The follow error occurs:
To replicate, create a Link for an Adapter, delete the Adapter and then attempt to edit the Link.
"An error has occurred: A link matching the id XXX could not be located" after deleting a Link
After deleting a Link, Adapter and Connector the following error is persistently appearing in the Netwealth UNIFYConnect DEV instance:
Could you please investigate and advise how to get rid of it?
Cannot compare dissimilar column types uuid and bigint at record column 1
All my UNIFYConnect adapters are showing the following error in the log, and all the Pending Changes are stuck in the adapter:
This is happening on the Netwealth UNIFYConnect instance.
Could you please investigate and fix or let me know what I've done wrong?
Patch attached for future reference, should go in the /Services/ directory.
Multiple DC server support for the AD Agent
A client has asked that we configure UNIFYConnect to round-robin through a number of DC IP addresses. I can't find an explicit way to do this in the Agent documentation.
How can I meet this requirement? Create my own DNS entry with multiple IP addresses?
Hi Adrian,
There's no explicit support for multiple server entries in the AD Agent. As you've pointed out, the easiest way is to use a DNS entry which contains multiple IP addresses - either on the service side or the customer side.
Remove LDAP adapter field name restriction for non-LDAP deployments
When deploying UNIFYBroker/Plus the LDAP name restriction for adapter field names is unnecessary - could you please offer a way to turn it off.
Upon review of this request, the modular way in which plugins and gateways interact require this restriction to still be in place, and would result in extra work if the solution was built and then an LDAP gateway added after the fact. Therefore the value in building this feature would not be realized in any measurable manner.
Customer support service by UserEcho
