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.
Identity Broker always logs to Application Event Log
Identity Broker v4.1 allows you to specify an event log to write to. Regardless of the event log chosen, it always writes to the application log.
If a custom log is chosen, it creates the event log (if it has sufficient rights), however it doesn't write to this log.
Identity Broker for chris21 delete "Termination Details" and perform "Synchronise Import" result in error/exception
This issue is encountered when testing and verifying [ IDB-13IDB-15
After deleting a "Termination Details" and then perform "Synchronisation Import" on the Termination connector result in the following exception:
20110117,00:03:31,Change detection engine poll started.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector started.,Normal 20110117,00:03:31,chris21 GTR EAI Communicator,Poll,Information,Started successfully.,Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Poll,Information,"Completed polling successfully after [00:00:00.0625000] duration. getEaiFile=EMTER;getEaiKey=Number Key:Count=1;detnumber=102967 Starting deletion of chris21 GTR EAI change files.",Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Poll,Information,Completed successfully after [00:00:00.0937500] duration.,Verbose 20110117,00:03:31,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal 20110117,00:03:31,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Termination Connector reported 1 changes. Duration: 00:00:00,Normal 20110117,00:03:31,Chris21 Termination Connector,GetEntities,Information,Started successfully.,Verbose 20110117,00:03:31,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal 20110117,00:03:31,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Termination Connector reported 1 changes. Duration: 00:00:00,Normal 20110117,00:03:31,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal 20110117,00:03:31,Chris21 Termination Connector,GetEntity,Information,Started successfully.,Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Get,Information,Started successfully.,Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Get,Error,"Exception occured after [00:00:00.0781250] duration. System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey)",Verbose 20110117,00:03:31,Chris21 Termination Connector,GetEntity,Error,"Exception occured after [00:00:00.0781250] duration. System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntity(MultiKeyValue entityId)",Verbose 20110117,00:03:31,Chris21 Termination Connector,GetEntities,Error,"Exception occured after [00:00:00.0781250] duration. System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntity(MultiKeyValue entityId) at Unify.Connectors.Chris21GtrConnectorBase`1.<GetEntities>b__4(MultiKeyValue entityId) at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntities(IEnumerable`1 entityIds)",Verbose 20110117,00:03:31,Change detection engine poll failed.,Change detection engine,Warning,"Change detection engine poll for connector Chris21 Termination Connector failed with reason GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected.. Duration: 00:00:00.2031250 Error details: System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntity(MultiKeyValue entityId) at Unify.Connectors.Chris21GtrConnectorBase`1.<GetEntities>b__4(MultiKeyValue entityId) at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntities(IEnumerable`1 entityIds) at Unify.Framework.ConnectorToPollingConnectorBridge.GetEntities(IEnumerable`1 entityIds) at Unify.Framework.EventNotifierReadingConnectorDecoratorBase`1.GetEntities(IEnumerable`1 entityIds) at Unify.Framework.ChangeDetectionPollJob.RunBase() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
The steps to reproduce:
- Terminate a user by creating the termination details record.
- Perform "Synchronise Import" on the Termination connector to obtain the delta change into Identity Broker entity repository. Success
- Perform "Delta Import" on FIM chris21 MA. Success
- Un-terminate the same user by deleting the termination details record
- Perform "Synchronise Import" on the Termination connector to obtain the delta change into Identity Broker entity repository. Failed, with the above error
Note: When this error occurred, the "eailst" record is removed (i.e no longer available in chris21). And no update to the Termination connector entity. The Person and Position connector does not encounter this issue.
The Identity Broker for chris21 Connector and Adapter configuration files attached. The Identity Broker log file containing the error also attached.
AdapterEngine.extensibility.config.xml
ConnectorEngine.extensibility.config.xml
Error occurred.jpg
UnifyLog20110117.csv
Deleting an existing connector throws exception
When deleting a populated connector in the latest IDB5 build the following error is received:
An exception of type 'System.Data.SqlClient.SqlException' occurred in Unify.IdentityBroker.Connector.Engine.dll but was not handled in user code
Additional information: Constraint 'FK_ChangeLog_Partition' does not belong to table 'Changes'.
The connector is still deleted successfully.
Transformations potentially retrieving whole join criteria instead of paged
As ToLookup will load all information in one hit, a new version should be created (StreamToLookup). Transformations should be changed to use this version (mainly group transformations).
Test to ensure they correctly page.
Ability to disable timings in Identity Broker for maintenance/inital load
Shane raising this on behalf of Andre from the previous weekend.
At times during a system migration, it is useful to be able to suspend automatic import schedules for connectors whilst still being able to operate the connectors manually.
AD connector - add filter to display UI
The filter that is part of the AD query is missing from the display UI component. It should be added.
2015-04-30 11_22_46-AD Connector - UNIFY Identity Broker.png
After changing connector agent old agent schema is still fetched
Changing a connectors agent or target table/file/etc then requesting the schema fetches the old schema. After a few minutes, requesting a schema fetches the correct schema
FIM export with required field as null fails silently
If FIM exports to an adapter whose connector has a non-key field set as required but the FIM MA does not (ie connector changed after xMA was generated) and that field in FIM is null, the export action will not be successful but no notification or error message is generated.
Request for deletion threshold to prevent mass deletion on imports
Hey Guys,
This request has come as a result of the deletion issues experienced at APRA on the weekend.
Is it possible to implement a feature to abort a connector import / change detection run if an unexpected number of deletes are imported?
I'm thinking something along the lines of a flag to enable/disable, and a threshold value (either a number of entities, or percentage value).
Ideally this would be configurable per connector (as some may legitimately and regularly experience large changes in existing data).
This kind of issue has happened previously on other sites, and a feature like this could prevent temporary data issues within a source system from having impact on downstream systems.
SQL server "Date" type is not supported?
SQL server "Date" type is not supported?
I have one field of type Date in SQL server.
But on import into Identity Broker, using the default field type that is configured for the schema provider (date), validation fails.
DateSQLServerNotSupported.jpg
Customer support service by UserEcho
