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.

  1. Forum: UNIFYBroker Forum
0
Answered

String attribute values with trailing spaces are trimmed

Bob Bradley 13 years ago • updated by anonymous 8 years ago • 14

The string "C1 Callam Offices, Easty Street, Woden ACT 2606; " was exported to the Placeholder Connector but the returned (confirming) import was "C1 Callam Offices, Easty Street, Woden ACT 2606;", causing ILM2007 to raise a "exported-change-not-reimported" warning.
Sure the data could be trimmed in a rules extension, but this is the same as the bug that was just fixed in the FIM 2010 Portal which was exhibiting the same behaviour (as well as incorrectly converting " " to " "). Whatever gets exported (right or wrong should always come back exactly the same.
The above problem will result in an infinite loop of export/import with Event Broker ... so it becomes a bigger issue when this happens. We're still in the DEV stage right now with CIT ...

0
Completed

IdB logs refer to Adapter GUIDs

Matthew Woolnough 11 years ago • updated by anonymous 8 years ago • 1

Adapter GUIDs are not available in the IdB UI.
,
Connectors are referred to by name

20130501,17:02:58,UNIFY Identity Broker,Adapter,Information,"Adapter import all entities to adapter space completed.
Adapter import all entities to adapter space 6e91a985-feb0-4d17-9ed9-191d9cd85c86 returned 8435 entities. Duration: 00:01:40.6744522",Normal
20130501,17:02:58,UNIFY Identity Broker,Adapter,Information,"Adapter
Adapter 6e91a985-feb0-4d17-9ed9-191d9cd85c86 page started reflection.",Normal
20130501,17:03:15,UNIFY Identity Broker,Adapter,Information,"Adapter
Adapter 6e91a985-feb0-4d17-9ed9-191d9cd85c86 page completed reflection. Duration: 00:00:16.9066828",Normal
20130502,04:10:41,UNIFY Identity Broker,Logging Engine,Information,Log file completed.,Minimal

0
Fixed

Excessive MultiRelationalTransformationContribution execution time

Tony Sheehy 12 years ago • updated by anonymous 8 years ago • 8

The MultiRelationalTransformationContribution can take a very long time to evaluate, as the current method re-evaluates the repository for each entity in the page.

0
Fixed

Multivalue DN generator transformation does not function correctly

Matthew Clark 12 years ago • updated by anonymous 8 years ago • 8

According to https://unifysolutions.jira.com/wiki/display/IDBXT306/Multi-value+Distinguished+Name+generator+transformation, the multivalue DN generator introduces a temporary field of MultivaluePart to an entity in order to run the DN generator across every value in a multivalue field. As this is not a field in the adapter schema, the field is not displayed in the dropdown when configuring the transformation, or in the DN generator for the transformation.

As such, a special type of DN generator should be introduced that is able to take a multivalue field in a component generator and produce the multivalue DN field accordingly. The transformation would no longer need to use a temporary field as a result. This would need to be done in such a manner that existing DN generators function correctly, and that it was only in the context of this transformation that the DN generator behaves this way (as multivalue fields in DNs can be used externally and simply print the multivalue as a string).

0
Answered

Identity Broker support for exporting to reference attributes (dns)

Bob Bradley 12 years ago • updated by anonymous 8 years ago • 7

For Identity Broker 3.* reference attributes are "forward (read) only". It is a standard IdM connector requirement to be able to export to reference attributes. While work-arounds are often (but not always) possible they are clumsy at best, and require double-processing of data (e.g. once for a reference flow, and once or more - in the case of multi-part keys - for a string flow). In most scenarios this requires storing of data redundantly (denormalisation) on the object being exported, and when this is necessary it usually creates additional overhead in deriving this data (e.g. for FIM Portal => FIM Metaverse => Identity Broker for a SQL connected system), e.g. through the use of FIM custom workflow activities. This creates not only inefficiency, but also potential loss of data integrity if there are workflow errors.

This idea came from this issue raised for DEEWR

0
Fixed

Can't provision group to placeholder connector after changing from dn.multi to string.multi.

Matthew Woolnough 11 years ago • updated by anonymous 8 years ago • 6

Error below is thrown when export group object to IdB.

20130114,22:36:07,Adapter request to save entity to adapter space failed.,Adapter,Warning,"Adapter request to save entity 58159829-60f9-4948-85c8-6be78e363005 to adapter space 7c0ca093-cbed-483d-b22e-8c4c20e28a41 failed with reason Unable to cast object of type 'Unify.Framework.MultiValue`1[Unify.Framework.DistinguishedNameValue]' to type 'System.Collections.Generic.IEnumerable`1[System.Object]'.. Duration: 00:00:00.0755100
Error details:
System.InvalidCastException: Unable to cast object of type 'Unify.Framework.MultiValue`1[Unify.Framework.DistinguishedNameValue]' to type 'System.Collections.Generic.IEnumerable`1[System.Object]'.
   at Unify.Framework.EntityMultiValueObjectTypeSchemaValidator`3.CreateValue(Object dataValue)
   at Unify.Framework.EntitySchemaFieldDefinition.CreateValue(Object dataValue)
   at Unify.Framework.EntitySchemaValueTransformer.Transform(IEntity baseValue)
   at Unify.Framework.Adapter.<>c__DisplayClass19.<SaveEntities>b__b(<>f__AnonymousType2`2 <>h__TransparentIdentifier6)
   at System.Linq.Enumerable.<>c__DisplayClass12`3.<CombineSelectors>b__11(TSource x)
   at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Unify.Framework.Adapter.SaveEntities(IEnumerable`1 entities, Boolean reflect)
   at Unify.Framework.Adapter.SaveEntity(IAdapterEntity entity, Boolean reflect)
   at Unify.Framework.CompositeAdapter.SaveEntity(IAdapterEntity entity)
   at Unify.Framework.AdapterNotifierDecorator.SaveEntity(IAdapterEntity entityToSave)
   at Unify.Framework.LDIFAdapter.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
   at Unify.Framework.LDIFAdapterServiceHostDecorator.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
   at SyncInvokeExportAdapterEntity(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.ProcessMessage4(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)",Normal
0
Completed

MA property not supported message to be improved or fixed

Matthew Clark 13 years ago in UNIFYBroker/Microsoft Identity Manager • updated by anonymous 8 years ago • 8

Refer to https://unifysolutions.jira.com/wiki/display/IDBFIM300/An+export+to+Identity+Broker+fails+with+an+ma-extension-error+and+the+Windows+Application+Event+Log+cites+an+InvalidOperationException+as+the+reason. In the cases where this error occurs, the error message should be improved to state that the generated distinguished name on the Identity Broker side is not matching the provisioning logic (or is not present).


Cannot provision incorrect DN.png
0
Fixed

Import all entitiesfrom connector Workday Employee failed with reason Value cannot be null.

André van der Westhuizen 9 years ago in UNIFYBroker/Workday • updated by anonymous 9 years ago • 4

The Workday Employee IdB connector fail with error: Import all entities
from connector Workday Employee failed with reason Value cannot be null.

The error in the log file is as follow:

Import all entities from connector failed.
Import all entities from connector Workday Employee failed with reason Value cannot be null.
Parameter name: value. Duration: 00:01:51.2800000
Error details:
System.ArgumentNullException: Value cannot be null.
Parameter name: value
at System.Xml.Linq.XAttribute..ctor(XName name, Object value)
at Unify.Product.IdentityBroker.OrganizationMembershipToXElementAdapter.Transform(WorkdayOrganizationMembership
sourceValue)
at
Unify.Product.IdentityBroker.MultiValueTypedAdapter`1.<Transform>b__0(TValue
v)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
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.Product.IdentityBroker.MultiValueStringAdapter.Transform(IEnumerable`1
sourceValue)
at
Unify.Product.IdentityBroker.WorkdayExtensions.SetValue[TEntity,TValue](IConnectorEntity
entity, IEntitySchema schema, HashSet`1 effectiveThroughOffsetFields, HashSet`1
subsequentFields, GroupedNameValueCollectionKey fieldName, TEntity baseEntity,
TEntity offsetEntity, TEntity subsequentEntity, Func`2 hasValue, Func`2
getValue)
at
Unify.Product.IdentityBroker.WorkdayWorkerToEntityAdapter.Transform(WorkdayWorker
sourceValue, WorkdayWorker offsetWorker, WorkdayWorker subsequentWorker)
at
Unify.Product.IdentityBroker.WorkdayWorkerConnector.<GetWorkers>d__c.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__19`1.MoveNext()
at
Unify.Framework.Collections.EnumerableExtensions.<ProduceAutoPages>d__a`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1
connectorEntities)
at
Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at
Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass29.<Run>b__27()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state) 

 

Change detection engine import all items failed.
Change detection engine import all items for connector Workday Employee failed
with reason Value cannot be null.
Parameter name: value. Duration: 00:01:51.3070000
Error details:
System.ArgumentNullException: Value cannot be null.
Parameter name: value
at System.Xml.Linq.XAttribute..ctor(XName name, Object value)
at
Unify.Product.IdentityBroker.OrganizationMembershipToXElementAdapter.Transform(WorkdayOrganizationMembership
sourceValue)
at Unify.Product.IdentityBroker.MultiValueTypedAdapter`1.<Transform>b__0(TValue
v)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
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.Product.IdentityBroker.MultiValueStringAdapter.Transform(IEnumerable`1
sourceValue)
at
Unify.Product.IdentityBroker.WorkdayExtensions.SetValue[TEntity,TValue](IConnectorEntity
entity, IEntitySchema schema, HashSet`1 effectiveThroughOffsetFields, HashSet`1
subsequentFields, GroupedNameValueCollectionKey fieldName, TEntity baseEntity,
TEntity offsetEntity, TEntity subsequentEntity, Func`2 hasValue, Func`2
getValue)
at Unify.Product.IdentityBroker.WorkdayWorkerToEntityAdapter.Transform(WorkdayWorker
sourceValue, WorkdayWorker offsetWorker, WorkdayWorker subsequentWorker)
at
Unify.Product.IdentityBroker.WorkdayWorkerConnector.<GetWorkers>d__c.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at
Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__19`1.MoveNext()
at
Unify.Framework.Collections.EnumerableExtensions.<ProduceAutoPages>d__a`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at
Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1
connectorEntities)
at
Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at
Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass29.<Run>b__27()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)
0
Answered

SAP HR Config Correction

Richard Courtenay 12 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 8 years ago • 2

Just noticed that at the page https://unifysolutions.jira.com/wiki/display/IDBSAP301/SAP+HCM+employee+connector

<infotypefield subTypeCode="0010" fieldName="USRID_LONG" connectorFildName="Email" />

should be

<infotypefield subTypeCode="0010" fieldName="USRID_LONG" connectorFieldName="Email" />

Minor, but took me a bit to spot

0
Completed

Improve Start service start

Matthew Woolnough 11 years ago • updated by anonymous 8 years ago • 3

Identity Broker service won't start if major processing is occuring.
Service should not be timing out. Look into using SetServiceStatus to inform the Service Control Manager that start up is not yet finished or other alternatives.

http://stackoverflow.com/questions/216401/windows-service-startup-timeout



Customer support service by UserEcho