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.
Return a more helpful error when an adapter accessed via ODATA is not enabled
When an non-enabled adapter is queried via ODATA the endpoint returns a 404 error. A different error with some descriptive text would make it easier to work out what has gone wrong.
Duplicated join target for NULL field value where there is no target with that field value
I am seeing: Baseline synchronization failed with the message "Source entity 'b5d56da5-a8af-4088-b98c-4b78a693b093' shares a join target with another source entity: 'fa457ecd-b5a7-4708-886b-747ca82da40a'. Cannot proceed with join.". See logs for more details.
Both source entity have a join field value of NULL, and there are no target entities with a join field value of NULL.
I tried deleting entities and reloading them, but the error remains. The mapping of field values through to other locker entities is not happening, and I would like to know if the join failure is the cause of this.
Hi Adrian
As the error message says, both of those source entities have the same join target, which may or may not exist until provisioning occurs. If the schema fields you're using can contain nulls and you want the sync to progress I'd recommend adding a Has Value filter on the join fields.
PowerShell connector operation timeout
Add a feature to allow a timeout to be specified for a PowerShell connector operation (Import All, etc). When the timeout expires, forcibly kill the PowerShell operation and log an error.
This came up because a connector hung for ten days in a UNIFYConnect environment until I noticed. All of the other connectors in the same connector exclusion group were blocked from running as well. I suggest a default timeout of one hour for most operations and 10 minutes for Import Changes.
Updating Google Connector Resets Agent
Hi,
Recently we ran into an issue with the Google Apps Connector where going into update the connector properties would set the agent to another rather than keeping the original value.
This caused an issue where we saved the connector without realizing the agent had been changed, causing the connector to import from another domain.
We can make sure the agent is set correctly before we make any updates, but it would be useful to have this behavior changed to avoid any issues accidents in future. Google Connector version is 5.3.2.0
Thanks
Test Connection operation for PowerShell connectors
Most UNIFYBroker agents have a Test Connection operation, but this can't be configured for PowerShell connectors. This morning my customer's PowerShell connectors were failing because Azure was reporting the MS Graph API to be overloaded and only accepting admin connections (“53300: remaining connection slots are reserved for non-replication superuser connections”).
Add a Test Connection facility to a PowerShell connector. This would tie in with https://voice.unifysolutions.net/en/communities/6/topics/4220-scheduled-execution-of-test-connection-on-agents
Google group membership exports
I have an environment where we are noticing some membership disparities for some google groups that are failing on export. My question around this is when a group membership fails to update for whatever reason, will the export process continue and try to amend the remaining membership changes for that group? Or will it simply throw the error back to MIM and move on to the next group in the export? UNIFYBroker and the Google Connectors are at the latest versions.
Thank you
The latter, the group update does not continue, and moves onto the next group.
Connection-aware join not persisting for outgoing link when join criteria field value changes - new adapter entity is created and old one is left behind
When a locker's Cloud Group Name field is updated this configuration causes the creation of a new adapter/connector entity. The old adapter/connector entity is retained. After the
The functionality is needed to allow solutions to have changes to entity key/join fields flow through to downstream systems.
AD connector Import Changes doesn't pick up changes to multivalued attribute (Import All does) for AD object type 'group' attribute 'member'
With the following AD connector configured:
When I use AD Users & Computers to change the DN of one of the objects in the 'member' attribute of a group and then run Import Changes the corresponding connector entity's member field is not updated and the old DN value is retained.
When I run Import All, the member attribute updates correctly with the new DN value.
JadeStar Position Occupancy Connector not surfacing PrimaryOccupancyIndicator attribute properly
There is an issue with the _KB_JadeStar Position Occupancy Connector in where the PrimaryOccupancyIndicator is not properly reflecting the values in JadeStar properly.
Details moved to comment. -BH
The PrimaryOccupancyIndicator for these two roles are both set to True in the connector. In the adapter, the Occupancy is joined with the Employee using PrimaryOccupancyIndicator as Priority and since there are two of these entries it chooses the first one which in this case is the wrong occupancy.
Could you please take a look at this connector and advise?
Bidirectional mapping data not flowing from Locker to Adapter
In a UNIFYConnect environment I have configured a Bidirectional mapping. For my locker entities there is a value in the field, and in the adapter entity the field is empty. When I run a Baseline Sync the values are not being copied to the adapter entities.
Locker:
Adapter:
There are no errors in the UNIFYBroker log file.
Closed due to no response. Feel free to re-open if you have any further information to share or the issue resurfaces.
Customer support service by UserEcho