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
Completed

Scheduled execution of Test Connection on agents

Adrian Corston 7 months ago in UNIFYBroker Service updated by Matthew Davis (Engineering Manager) 2 months ago 1

An automated periodic execution of the Test Connection functionality on an agent for UNIFYMonitor to pick up and report on would give UNIFY early warning that a low level service problem exists.

[Bob's suggestion]

Answer

Hi Adrian,

This could be completed using the Scheduled Jobs feature of the UNIFYBroker logging engine. This gives access to the $components.AgentEngine component, which has a method void Test(Guid agentId) that could be used to execute tests. Alternatively you could call the REST API from a scheduled job to execute the task.

0
Under review

Change detection engine unscheduled for connector X failed with reason Circular dependency detected while attempting to determine base key of A. Current working key: A Process keys: A, B

Adrian Corston 1 month ago in UNIFYBroker Service updated 1 month ago 2

This error is being written to the UNIFYBroker logs in multiple UNIFYConnect environments.  I deleted all transforms that referred to those fields, removed references to the fields from links, and then recreated them all, but it didn't stop the error from appearing.

0

Scheduled connector Import All operations for an connector exclusion group stopped running

Adrian Corston 2 months ago in UNIFYBroker Service 0

A few weeks ago all the connectors in a connector exclusion group inexplicably stopped running.  Scheduled Import All operations are running OK on connectors not in the connector exclusion group.  There does not appear to be any running Import All operations on any of the connectors in the group.

0
Answered

Idb Connector - The remote server returned an error: (500) Internal Server Error

Abhishek S 2 months ago in UNIFYBroker Service updated by Matthew Davis (Engineering Manager) 2 months ago 1

Hi,

Please let me know what could be the reason for 500 internal server error here.

Thank you


20210701,00:28:13,UNIFY Identity Broker,Connector,Warning,"Update entities to connector failed.

Update entities [Count:1] to connector TechOne SMS Student Management Users failed with reason The remote server returned an error: (500) Internal Server Error.. Duration: 00:00:02.1884079

Error details:

System.Management.Automation.RuntimeException: The remote server returned an error: (500) Internal Server Error. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.

at System.Net.HttpWebRequest.GetResponse()

at CallSite.Target(Closure , CallSite , Object )

--- End of inner exception stack trace ---

at Unify.Product.IdentityBroker.PowerShellConnector.Execute(String script, IEnumerable`1 inputEntities, IEnumerable`1 inputKeys)

at Unify.Product.IdentityBroker.EventNotifierUpdatingConnectorDecorator.UpdateEntities(IEnumerable`1 entities)

at Unify.Product.IdentityBroker.Adapter.UpdateEntities(IEnumerable`1 entities, EntityToConnectorEntityBridge[]& connectorEntities)

at Unify.Product.IdentityBroker.Adapter.UpdateEntities(IEnumerable`1 entities)

at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.UpdateEntity(IAdapterEntity entityToSave)

at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.UpdateEntity(IAdapterEntity entityToSave)

at Unify.Product.IdentityBroker.LDIFAdapterBase.HandleExportUpdate(IAdapter adapter, IAdapterEntitySaveChange pendingUpdate)

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)",Normal

Answer

Hi Abhishek,

That call is made inside a PowerShell connector, so it appears as though the web server that is attempting to be called is not available or throwing an error during the execution of the script.

0
Not a bug

Multivalue Group tranform didn't update field when source field was updated

Adrian Corston 2 months ago in UNIFYBroker Service updated by Matthew Davis (Engineering Manager) 2 months ago 6

I have two MV Group transforms in an adapter:

The MemberUPNs field updated correctly, but MemberAzureIDs did not.  There are six values in MemberUPNs, but only two in MemberAzureIDs.  Manual validation confirms that the matching values in the second transform's connector are present and correct.  I do not know what the old value of MemberUPNs was.

I believe the change occurred on 30/6/21 some time in the hour or two prior to 8am, but unfortunately the corresponding log file has already been deleted.

Answer

Closing this item as it appears to be a misdiagnosis. Feel free to re-open if the issue surfaces again and presents the same way.

0
Answered

Error on Techone SMS staff Connector - TechOne SMS Staff failed with reason The key has been duplicated

Abhishek S 2 months ago in UNIFYBroker Service updated by Matthew Davis (Engineering Manager) 2 months ago 1

Hi,
Below is from the IDB Logs; I cannot find the duplicate value for the user accounts. Could you please let me know what could be another issue here?
Thank you


Connector Processing page 1 for connector TechOne SMS Staff failed with reason The key CARLSSOS has been duplicated.. Duration: 00:00:00.9687755.

Error details:

System.ArgumentException: The key CARLSSOS has been duplicated.

at Unify.Product.IdentityBroker.EntityRepositoryExtensions.DuplicateKeyBase(MultiKeyValue arg1)

at Unify.Framework.Collections.EnumerableExtensions.ToDictionaryWithKeyClashError[TKey,TValue,TOriginal](IEnumerable`1 originalEnumerable, Func`2 keySelector, Func`2 valueSelector, Action`3 duplicateAction)

at Unify.Product.IdentityBroker.EntityRepositoryExtensions.ConvertConnectorEntitiesWithRepositoryEntities(IEnumerable`1 connectorEntities, IMultiKey`1 schemaKey, IQueryable`1 sourceEntities, Guid connectorId, IEnumerable`1 originalEntities)

at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetectionOnConnectorEntityPage(IEnumerable`1 connectorEntities, Int32& index, Int32 entitiesProcessedSoFar, IEntityChangesReportGenerator`2 reportGenerator)

at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.<>c__DisplayClass3.b__0(IEnumerable`1 page)

at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.ThreadsafeItemEvaluator.Evaluate()",Normal

20210704,15:30:57,UNIFY Identity Broker,Connector Processor,Information,"Connector Processing started.

Connector Processing started for connector TechOne SMS Staff (page 2)",Normal

20210704,15:30:58,UNIFY Identity Broker,Connector Processor,Information,"Connector processing failed.

Connector Processing page 2 for connector TechOne SMS Staff failed with reason The key GOODMANN has been duplicated.. Duration: 00:00:01.4374637.

Error details:

System.ArgumentException: The key GOODMANN has been duplicated.

at Unify.Product.IdentityBroker.EntityRepositoryExtensions.DuplicateKeyBase(MultiKeyValue arg1)

at Unify.Framework.Collections.EnumerableExtensions.ToDictionaryWithKeyClashError[TKey,TValue,TOriginal](IEnumerable`1 originalEnumerable, Func`2 keySelector, Func`2 valueSelector, Action`3 duplicateAction)

at Unify.Product.IdentityBroker.EntityRepositoryExtensions.ConvertConnectorEntitiesWithRepositoryEntities(IEnumerable`1 connectorEntities, IMultiKey`1 schemaKey, IQueryable`1 sourceEntities, Guid connectorId, IEnumerable`1 originalEntities)

at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetectionOnConnectorEntityPage(IEnumerable`1 connectorEntities, Int32& index, Int32 entitiesProcessedSoFar, IEntityChangesReportGenerator`2 reportGenerator)

at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.<>c__DisplayClass3.b__0(IEnumerable`1 page)

at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.ThreadsafeItemEvaluator.Evaluate()",Normal

20210704,15:31:23,UNIFY Identity Broker,Connector Processor,Information,"Connector Processing started.

Connector Processing started for connector TechOne SMS Staff (page 3)",Normal

20210704,15:31:25,UNIFY Identity Broker,Connector Processor,Information,"Connector processing failed.

Connector Processing page 3 for connector TechOne SMS Staff failed with reason The key ANDREWE has been duplicated.. Duration: 00:00:01.9218138.

Error details:

System.ArgumentException: The key ANDREWE has been duplicated.

at Unify.Product.IdentityBroker.EntityRepositoryExtensions.DuplicateKeyBase(MultiKeyValue arg1)

at Unify.Framework.Collections.EnumerableExtensions.ToDictionaryWithKeyClashError[TKey,TValue,TOriginal](IEnumerable`1 originalEnumerable, Func`2 keySelector, Func`2 valueSelector, Action`3 duplicateAction)

at Unify.Product.IdentityBroker.EntityRepositoryExtensions.ConvertConnectorEntitiesWithRepositoryEntities(IEnumerable`1 connectorEntities, IMultiKey`1 schemaKey, IQueryable`1 sourceEntities, Guid connectorId, IEnumerable`1 originalEntities)

at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetectionOnConnectorEntityPage(IEnumerable`1 connectorEntities, Int32& index, Int32 entitiesProcessedSoFar, IEntityChangesReportGenerator`2 reportGenerator)

at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.<>c__DisplayClass3.b__0(IEnumerable`1 page)

at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.ThreadsafeItemEvaluator.Evaluate()",Normal

Answer

Hi Abhishek,

This means that while importing data from the system (TechOne SMS Staff), there are duplicate keys coming through. UNIFYBroker can't process the data if the primary key is not unique.

Check the system that the data is being imported from to see if there are records with duplicated keys.

0
Answered

Unify Identity Broker- The transaction has aborted Error

Abhishek S 3 months ago in UNIFYBroker Service updated 2 months ago 4

Hi,

We are using Unify identity Broker version v4.1.1 Revision #1 and one of the Connector is having below error  

Import All Run

Change detection engine import all items for connector Aurion Staging Staff Details Connector failed with reason The transaction has aborted.. Duration: 00:12:00.6306978

Based on my understanding, Connector is timing out if it's runs more than 10mins and I'm unable to find the set timeout threshold field limit in Identity broker. Can you please confirm where it could be set  or is there option to set the version we have.

Thank you

Below is from the logs

Direct communicator
Exception occured after [00:10:18.3617284] duration.

System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout
--- End of inner exception stack trace ---
at System.Transactions.TransactionStateAborted.BeginCommit(InternalTransaction tx, Boolean asyncCommit, AsyncCallback asyncCallback, Object asyncState)
at System.Transactions.CommittableTransaction.Commit()
at System.Transactions.TransactionScope.InternalDispose()
at System.Transactions.TransactionScope.Dispose()
at Unify.Framework.Data.AdoNetDataControl.ExecuteDataSetQuery(DataSet resultSet, String commandText, IEnumerable`1 parameters, String[] tableNames, CommandType commandType)
at Unify.Framework.Data.AdoNetDataControl.ReturnDataSetQuery[T](String commandText, IEnumerable`1 parameters, String[] tableNames, CommandType commandType)
at Unify.Product.IdentityBroker.DirectCommunicatorBase`1.GetAllEntitiesDataTable()
at Unify.Product.IdentityBroker.DirectCommunicatorBase`1.GetAllEntities()
Answer

Hi Abhishek,

The timeout for the database connector can be set on the agent that is used for that connector. In this case that appears to be the SQL server agent, which has a configuration setting for Operation Timeout.

You can find details on that configuration here: SQL Server Database Agent / UNIFYBroker knowledge / UNIFY Solutions

0
Declined

Understand change detection better

Adrian Corston 4 months ago in UNIFYBroker Service updated by Matthew Davis (Engineering Manager) 2 months ago 2

I have these adapter transforms set up:

Changes to the EmployeeNumbers attribute should flow through the following other attributes in this order:

  1. MemberADUPNs (first MVG transform)
  2. MemberAzureUPNs (PowerShell transform)
  3. MemberAzureIDs (second MVG transform)

Sometimes when EmployeeNumbers values are updated I see MemberADUPNs and MemberAzureUPNs updating correctly, but MemberAzureIDs does not update with the new value like it should.

Q1. Is this because "PowerShell transforms break change detection"?  i.e. UNIFYBroker doesn't know that it needs to run the second MVG transform to update MemberAzureIDs, because it has no way to know that that MemberAzureUPNs may be updated by the PowerShell transform?

Q2. Could Beau's new "Register-Contribution" cmdlet be used in the PowerShell transform to make it so it does?

0
Under review

Add ability to recreate deleted future-dated adapter changes (Time Offset Flag etc)

Adrian Corston 4 months ago in UNIFYBroker Service updated by Matthew Davis (Engineering Manager) 3 months ago 1

In ticket https://voice.unifysolutions.net/en/communities/6/topics/4238-time-offset-flag-didnt-re-evaluate-when-date-threshold-was-passed?redirect_to_reply=21889# Beau mentions that:

Add functionality to recreate deleted future-dated adapter changes to the UNIFYBroker UI (and API).

This should also be called automatically after a Clear Adapter Changes operation completes, because it is unlikely that there are any conceivable scenario where future-dated changes should not be restored, and without them UNIFYBroker does not operate sensibly (i.e. expected transforms silently fail to trigger when the configuration suggests they should).

Also, update the Clear Adapter Changes documentation in Voice to indicate that after running Clear Adapter Changes some transforms will no longer work correctly until Clear Precalculated Entities is run or all relevant date fields on all adapter entities are updated.

0
Under review

Time Offset Flag didn't re-evaluate when date threshold was passed

Adrian Corston 4 months ago in UNIFYBroker Service updated 4 months ago 22

I have the following Time Offset Flag adapter transformation configured:

For the problematical entity the EndTimestampUTC field is "4/22/2021 12:00:00 PM" (i.e. midnight at the start of April 23rd in my customer's timezone - NZ), so the corresponding UTC timestamp for the threshold comparison should be "5/7/2021 12:00:00 PM" (i.e. midnight at the start of May 8th in NZ timezone).  EndTimestampUTC was changed to that value on May 7 (i.e. before UTC 5/7/2021 12:00:00 PM) but even though today is now May 10th the PostEndPlus14 field hasn't been re-evaluated to "Yes" as I would have expected (i.e. transition from the ">" case to the "<" case).

To allow a better chance to debug I have not run a Generate Changes on the adapter yet.