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.
Entities that fail validation are still having changes registered against them
An import against a connector with entities that fail validation will generate changes even for those failing entities.
My setup currently has two connectors:
- e5d00f42-3725-4897-b909-73149f22c8cd (tony)
- 69e858d9-ef5e-488b-88cb-a75f3a8a1ed5 (AR)
One adapter:
- b78abc46-dc95-40d8-a2ef-37fcf2986e82 (AR Adapter)
An import against AR generates 20 changes for the 20 entities that are failing validation.
Each time, 20 entries appear in the changes table, with entity id's that cannot be found elsewhere in the database.
IdB4: How long until the error notification disappears?
I had an error on my CSV connector - incorrect number of columns. Its put the next to it to denote the error. The error is resolved and several successful imports have occured but the icon is still there.
How long until it disappears automatically?
This appears on the home page. Its not on the Connectors page at all.
Updating an adapter after added to a group makes the group uneditable
After updating the name of an adapter that had been added to an adapter group, the adapter disappeared from the group membership. Attempting to update the group details or memberships following this resulted in the following error:
System.ServiceModel.FaultException`1System.ServiceModel.ExceptionDetail: A group could not be found that corresponds to the provided id, '1f383ffd-89d3-437f-821e-e4873effd757' (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: Unify.Framework.UnifyEngineException: A group could not be found that corresponds to the provided id, '1f383ffd-89d3-437f-821e-e4873effd757' at Unify.Product.IdentityBroker.GroupEngineBase`1.<>c_DisplayClassc.<GetGroup>b_b()
at Unify.Framework.ExtensionMethods.WaitOnMutex(Mutex mutex, Action work)
at Unify.Product.IdentityBroker.GroupEngineBase`1.GetGroup(Guid groupId)
at Unify.Product.IdentityBroker.GroupEngineNotifierDecorator`1.GetGroup(Guid groupId)
at Unify.Product.IdentityBroker.GroupEngineAccessorBase`2.GetGroup(Guid groupId)
at Unify.Product.IdentityBroker.IdentityServiceCollector.GetConnectorGroup(Guid id)
at SyncInvokeGetConnectorGroup(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at S...).
Object deletes on composite adapter don't work
Deletes via a composite adapter fail due to a cast exception:
System.Exception: Error occurred when attempting to save entity with distinguished name
CN=100500
Error:
Unable to cast object of type 'Unify.Product.IdentityBroker.OperationalAdapter' to type 'Unify.Product.IdentityBroker.IAdapter'.
at Unify.Product.IdentityBroker.CompositeAdapter.DeleteEntityExceptionHandler(Action`1 adapterDeleteAction, IEnumerable`1 entityIds)
at Unify.Product.IdentityBroker.CompositeAdapter.DeleteEntity(Guid entityId)
at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.DeleteEntity(Guid entityId)
at Unify.Product.IdentityBroker.LDIFAdapterBase.ExportChanges(ExportedLDIFForAdapter exportedLdifForAdapter)
at SyncInvokeExportChanges(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
at Unify.Product.IdentityBroker.IdentityBrokerManagementAgentProxy.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
at Unify.Product.IdentityBroker.IdentityBrokerManagementAgent.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
Connectors being added to groups shouldn't need to be disabled
IDB-355 initially required that connectors be disabled to be added to groups. It was decided that this requirement was silly to enforce as it didn't add anything to the solution and would require work in the future to maintain this restriction.
The changed requirement, however, was missed.
Copy transformation error message is not obvious
Attempting to add a "Copy" transformation that contains the default values
singleval insert into singleval
Results in a transformation that adds the same field twice to the adapter schema. The error message on the transformation though is as follows:
Specified argument was out of the range of valid values. Parameter name: key
Schema provider select which fields to apply
With some schema providers potentially having 100 fields, the ability to optionally select which fields are applied becomes quite important.
First determine the feasibility of this, and make sure it won't take much longer than the estimate before commencing.
Update the schema provider to have check-boxes next to each field (default checked) and only apply those that are checked. Also include a check all / uncheck all checkbox at the top.
Throw warning if IdB tries to update an attribute on a connector that does not exist
Currently, When Group Membership information is read in via a transformation, if you write back to this attribute the data disappears into the ether, with no warning or errors thrown.
An error or warning should be thrown.
Investigate whether trailing spaces being stripped are detected as a change
From UNISC-10, trailing spaces were causing issues with a join. The issue wasn't resolved until the connector was cleared and reimported. The trailing spaces should have been removed during regular connector imports. Investigate whether trailing spaces are detected as a change (and subsequently reflected), and also the scenario with the key only changing.
Cannot request Schema - Byte validator missing
When attempted to request schema for the InnerRange Concept 4000 Virtual User connector I recieve the following error:
Value cannot be null. Parameter name: There are no known default validators that support the Byte value type.
Customer support service by UserEcho
