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.

0
Answered

Older Installations

Daniel Walters 7 years ago updated by Adam van Vliet 7 years ago 2

Hi,

Can I get the installation for broker 4.1.1. I want it for two things, first is to lab an upgrade if I get a chance, the second thing is because the PS process for an IdB upgrade is to run 4 and 5 in parallel so that we can compare an old and new MA. To run in parallel, I'll need to install 4 on another server while the original server is upgraded. The v4 instance will then be decommissioned once the testing has been done.

Answer

Hi Dan,

All available downloads can be found at https://downloads.unifysolutions.net/ 

0
Answered

Aderant Expert Connector for UNIFYBroker

Daniel Walters 7 years ago in UNIFYBroker/Aderant Expert updated by anonymous 7 years ago 10

Is this a custom connector? I can't see it in the KB. What's the situation if it is a custom connector? It's installed with a v4IdB currently but I don't have the connector installation. Would further development be required for the connector to work with 5?

Answer
Adam van Vliet 7 years ago

The intention was always to commercialise it, but the API's were not ready in time so we had to go straight to the database. Since then client specific fields were also added in. The connector was upgraded for a new version of Aderant Expert, but I don't believe they ended up using it. The connector would need to be upgraded, please loop in Richard.

0
Answered

Upgrade for IdB4

Daniel Walters 7 years ago updated by Matthew Davis (Technical Product Manager) 7 years ago 5

I have a couple of questions around an upgrade from idb4 to UnifyNow

  • How long should it take?
  • It's not in-place is it?
  • What would be the step-by-step for migrating config? ie. I can't look at the config if I've already uninstalled 4
  • What's the process for migrating between environments? Do I just copy the extensibility folder and then update connection strings/credentials in the browser?
  • Why is SQL server 2014 recommended?
Answer
Adam van Vliet 7 years ago
How long should it take?

Which part are you referring to? If it's the installation, a few minutes. If you mean end-to-end, including the new MA's, you'd be better placed to dig into PS references as it has been done numerous times there.

It's not in-place is it?

https://voice.unifysolutions.net/knowledge-bases/7/articles/2938-upgrading-the-unifybroker-service

What would be the step-by-step for migrating config? ie. I can't look at the config if I've already uninstalled 4

https://voice.unifysolutions.net/knowledge-bases/7/articles/2938-upgrading-the-unifybroker-service

What's the process for migrating between environments? Do I just copy the extensibility folder and then update connection strings/credentials in the browser?

https://voice.unifysolutions.net/knowledge-bases/7/articles/2933-migrating-unifybroker-between-environments

Why is SQL server 2014 recommended?

It's not, it says "or newer" (https://voice.unifysolutions.net/knowledge-bases/7/articles/2920-unifybroker-installation-prerequisites)

0
Fixed

UNIFYBroker Entity Search Throwing an error

Hayden Gray 7 years ago updated by Beau Harrison (Senior Product Software Engineer) 6 years ago 4

Hi Guys,

When clicking on the entity count to do an entity search (Both Connector and Adapter). I can't seem to perform an entity search. I get the following error: 

Error

System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Unify.Connect.Web.IdentityBrokerEntitySearchController.CurrentEntities(EntityRetrievalInformation`1 information)
at Unify.Connect.Web.IdentityBrokerEntitySearchController.<EntityData>d__35.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at lambda_method(Closure , Task )
at System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass34.<BeginInvokeAsynchronousActionMethod>b__33(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3c()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass45.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3e()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass30.<BeginInvokeActionMethodWithFilters>b__2f(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass1e.<>c__DisplayClass28.<BeginInvokeAction>b__19()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass1e.<BeginInvokeAction>b__1b(IAsyncResult asyncResult)
---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.<---

 DataTables Error

This error hasn't always occurred, however recently the error is appearing for connectors/adapters with high entity counts (lower entity count connectors/adapters seem to be fine).

Current IDB version: v5.3.1

Troubleshooting so far:

* Restart the UNIFYBroker Service

* Rebuilt all indexes on the UNIFYBroker Database

Let me know if you need more information.

Thank

0
Answered

Any known issues with C21 upgrades?

Daniel Walters 7 years ago in UNIFYBroker/Frontier ichris/chris21 updated by Adam van Vliet 7 years ago 1

HSF are upgrading their C21 instance over the weekend so I just wanted to check if there's any known issues with upgrades and the broker c21 connector. They say it's an Engine update, going to version 8.16.5. They're using Identity Broker version 4. Any known issues?

Answer
Adam van Vliet 7 years ago

Hi Daniel,

None that I have been made aware of. As you haven't mentioned what version of the connector, or what version of chris21 they are upgrading from, just ensure that you're on the latest available connector, as there was a change to the way logons were performed quite some time ago that we had to update the connector for (logonapplication became an invalid argument). Additionally, as with any upgrade (and in line with Frontier advice), ensure that the integration is included in the upgrade and test plan.

Thanks.

0
Fixed

Aurion export error: Object must implement IConvertible. at System.Convert.ChangeType

When trying to export Contact_Phone_Number to Aurion I get "Other", "One or more errors occurred" reported in MIM.

The error is on the screen in the Adapter (though not in the Broker log file). I've pasted the error below.

Aurion should already be set up to allow exports to this field as the existing solution does that. I've checked the field name and mapping is the same in the Connector config file for both new and old solutions.

Broker version: 5.3.1. Revision #0

Aurion connector version: 5.3.0.0

It's trying to export a string value for two entities. The export flow rule from MIM is a direct flow and the metaverse attribute is a single-valued string.

Her's the error message from the Adapter screen:

Adapter update entities [Count:2] to adapter Aurion Personnel (549d90e8-e7df-4729-9e4c-58c73d1c98d3) failed with reason System.AggregateException: One or more errors occurred. ---> 
Unify.Product.IdentityBroker.EntitySchemaValidationException: Provided value System.Linq.Enumerable+d__14`2[Unify.Framework.DistinguishedNameValue,System.String] failed validation for type String ---> System.InvalidCastException: Object must implement IConvertible.
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at Unify.Product.IdentityBroker.EntityObjectTypeSchemaValidator`2.CreateValue(Object dataValue)
--- End of inner exception stack trace ---
at Unify.Product.IdentityBroker.EntityObjectTypeSchemaValidator`2.CreateValue(Object dataValue)
at Unify.Product.IdentityBroker.DistinguishedNameGeneratorReverseTransformation.Transform(IEntity[] sourceValue)
at Unify.Framework.AggregateArrayedValueAdapter`2.<>c.b__2_0(TElement[] current, IValueAdapter`2 valueAdapter)
at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func)
at Unify.Framework.AggregateArrayedValueAdapter`2.Transform(TElement[] baseValue)
at Unify.Framework.AggregateArrayedValueAdapter`2.<>c.b__2_0(TElement[] current, IValueAdapter`2 valueAdapter)
at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func)
at Unify.Framework.AggregateArrayedValueAdapter`2.Transform(TElement[] baseValue)
at Unify.Product.IdentityBroker.Adapter.GetReverseTransformedEntities(IEnumerable`1 entities)
at Unify.Product.IdentityBroker.Adapter.d__112.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Unify.Product.IdentityBroker.Adapter.d__111.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Adapter.d__70.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Adapter.d__69.MoveNext() --- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Unify.Framework.Auditing.AuditingExtensions.<>c__DisplayClass7_0`1.b__0(Task`1 t)
at Unify.Framework.Auditing.AuditingExtensions.<>c__DisplayClass5_0`1.b__0(Task`1 t)
at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.AdapterNotifierDecorator.d__39.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.RequestHandlers.BulkRequestEntityGroupProcessor.d__18.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.RequestHandlers.BulkRequestEntityGroupProcessor.d__12.MoveNext() ---> (Inner Exception #0) Unify.Product.IdentityBroker.EntitySchemaValidationException: Provided value System.Linq.Enumerable+d__14`2[Unify.Framework.DistinguishedNameValue,System.String] failed validation for type String ---> System.InvalidCastException: Object must implement IConvertible.
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at Unify.Product.IdentityBroker.EntityObjectTypeSchemaValidator`2.CreateValue(Object dataValue) --- End of inner exception stack trace ---
at Unify.Product.IdentityBroker.EntityObjectTypeSchemaValidator`2.CreateValue(Object dataValue)
at Unify.Product.IdentityBroker.DistinguishedNameGeneratorReverseTransformation.Transform(IEntity[] sourceValue)
at Unify.Framework.AggregateArrayedValueAdapter`2.<>c.b__2_0(TElement[] current, IValueAdapter`2 valueAdapter)
at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func)
at Unify.Framework.AggregateArrayedValueAdapter`2.Transform(TElement[] baseValue)
at Unify.Framework.AggregateArrayedValueAdapter`2.<>c.b__2_0(TElement[] current, IValueAdapter`2 valueAdapter)
at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func)
at Unify.Framework.AggregateArrayedValueAdapter`2.Transform(TElement[] baseValue)
at Unify.Product.IdentityBroker.Adapter.GetReverseTransformedEntities(IEnumerable`1 entities)
at Unify.Product.IdentityBroker.Adapter.d__112.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Unify.Product.IdentityBroker.Adapter.d__111.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Adapter.d__70.MoveNext() --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Adapter.d__69.MoveNext()<--- . Duration: 00:00:00.0156171
0
Answered

Reasons for Upgrade?

Daniel Walters 7 years ago updated by Matthew Davis (Technical Product Manager) 7 years ago 1

I have a customer on version 4 of Identity Broker and there's some interest in an upgrade. What is the current version of UnifyBroker? And what reasons are there to give them to upgrade from 4? Their main complaint is with the connector browsing and searching being unresponsive and ambiguous as to whether a search has loaded or no results have returned. Has there been work done on the search/browse for connectors? What else is good about the new version compared to 4?

Answer

Hey Dan,

The current version of Identity Broker is 5.3.1.1.

For a complete list of high-level features since 4.0, please see this link:

https://voice.unifysolutions.net/knowledge-bases/7/articles/3058-unifybroker-release-notes

The UI has been changed to use a REST endpoint, and improvements made so there's no longer issues with the browsing and searching being unresponsive. 

The other main benefits of upgrading include:

  • using LDAP for data between IDB and MIM, which allows for faster data and more flexible MA configuration
  • Powershell adapter transformations
  • Auditing

Identity Broker 4.x is also out of support, so it would be in their best interests to upgrade. 5.3 will be supported until at least 03/2023.

0
Completed

Where to find Credentials from FIM

Daniel Walters 7 years ago updated by Matthew Davis (Technical Product Manager) 7 years ago 4

I'm working with an existing implementation and looking to do a refresh of a dev environment with what's in prod. I'll need all the MA credentials to do that and no one has a record of the identity broker credentials. They're using version 5 (the one that shows as version 0.0.5). Is there anywhere I can lookup or reset the credentials that are used to connect to Identity Broker from the FIM IdB Management Agent?

Answer

Hi Dan,

There's no way to retrieve existing credentials, but you can create a new account which will work the same.

See this link for documentation on achieving this: https://voice.unifysolutions.net/knowledge-bases/7/articles/2948-configuring-ldap-gateway-authentication-accounts 

0
Answered

SQL Connector/Adapter

Daniel Walters 7 years ago updated by Adam van Vliet 7 years ago 8

I haven't worked with UNIFYBroker in some time. I've got a SQL Connector/Adapter here and I'm looking for the table that it's connecting to. The agent has a connection string in it that specifies the server and the database but not the table name and the connector doesn't contain the table name either. I can see when I create a new connector I can choose a schema provider. Can you explain how a connector knows which table it is connecting to or does it pool all the attributes from all tables in the database - I thought that's what an adapters do. There's no UNIFYBroker\SQL category so I've left uncategorized.

Answer

You can also get back to that view by editing the connector, however the table name should be visible on the connector details page.

The table name should also definitely be in the extensibility file and should look like this:

<Extended>
    <communicator owner="dbo" table="mytable" readThreshold="1000" />
</Extended>

If this isn't the case, can you provide screenshots and the extensibility file?

0
Fixed

"A task was cancelled' when refreshing connector schema

Carol Wapshere 7 years ago updated by Beau Harrison (Senior Product Software Engineer) 7 years ago 5

After upgrading to Aurion connector 5.3.0.0, on Broker 5.3.1.1, I cannot update the schema for most of my connectors. After choosing "Query fields" it appears to run for 1-2 minutes then fails with "A task was cancelled". I can't see anything in the IDB log file relating to this. The Full Import of the connector runs.