MIM Event Broker Forum

Welcome to the community forum for MIM Event 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.

+7
Completed

REST API to access Event Broker service methods directly

Bob Bradley 4 years ago updated by anonymous 3 years ago 1

I know this is somewhere on the roadmap, but I thought I'd give you a specific example of how I would like to use this to lookup the Operation List name for a corresponding guid from within a PowerShell script. I know this method exists on the WCF endpoint because it is exposed in the WSDL. However it is not a simple exercise to access this from PowerShell.


For the time being I have a work-around which relies on looking up the Event Broker registry key to determine the extensibility file path, then querying the operations extensibility xml directly. However the limitation here is that this will only work if the script is running locally on the Event Broker service host.

Answer
anonymous 3 years ago

Now that this has been proven in Identity Broker we'll look at this for MIM Event Broker.

+5
Not a bug

UNIFYNow Upgrade Failing operation lists afterwards

Daniel Walters 3 months ago updated by Matthew Davis (Engineering Manager) 3 months ago 5

Just upgraded UNIFYNow (4.0.0.1 to 4.0.4.0) after upgrading broker (5.2.0.2 to 5.3.2.0) and alot of the UNIFYNow operations lists that are supposed to trigger IDB operations lists are failing all with the same error. 

Answer

The field the error message is quoting was removed in v4.0.3. Please check for and remove any old patches, as we discuses in your earlier issue.

+4
Completed

Event Broker agent wizard leads to "The server is unwilling to process the request" exception for specific OU

Bob Bradley 4 years ago updated by anonymous 2 years ago 10

When an OU is configured for an AD agent that is NOT the domain root (e.g. "OU=Employees,DC=mim2016,DC=local") we get the following exception when the generated incoming operation list is activated:


Operation faulted: The server is unwilling to process the request. - Please see the log viewer for more details.

This is because the AD Sync Changes check operation uses the full DN for the "Domain" property instead of the DC part only (i.e. "DC=mim2016,DC=local").


To avoid this error the AD sync changes operation needs to extract the DC DN from the full DN supplied.

Answer
anonymous 2 years ago

Fixed in 4.0

+2
Fixed

Event Broker Operation management halts with Blank screen

Shane Day (Chief Technology Officer) 4 years ago updated by anonymous 3 years ago 4
Hi Product Team!
Attempting to delete operations from "/Operation" (Operation Lists Page) is met with a blank screen. The URL redirects to "/Operation/ModifyOperationLists" but the page is blank.
The only way to delete operations via the GUI is to Open the operation from the operations list. Click Actions and Delete from within the Operation. Even attempting to delete the operation this way acts strange.. When attempting to delete from within the operation the "Are you sure" window pops up for a second and automatically submits the deletion without confirmation.
Happy to ellab on this if required.

Item originally from Ryan Crossignham from PRODUCT-389

screen2.png - Latest 21/Sep/15 4:47 PM - Ryan Crossingham
+1
Completed

Email logger does not support multiple TO email addresses

Bob Bradley 3 years ago updated by anonymous 3 years ago 4

Presently the TO address supports only a single target email address. However this field is multi-valued in the sendmail API and the logger could easily be extended to support this. There is no tooltip on this field so it was not intuitive that this restriction applied - however attempts using "," and ";" delimiters both failed. Work-arounds include setting up multiple loggers, or using a distribution list. However there are times when this would still be handy - especially when d-lists are not easily modified or the requirement is only temproary.

Answer
anonymous 3 years ago

Added ability to have logs emailed to multiple addresses. Will be included in the next release.

+1
Completed

Incorporate progress bar on executing operations

Bob Bradley 4 years ago updated by anonymous 2 years ago 3

With the release of Ryan Newington's latest Lithnet miis-powershell module it occurred to me that it may be possible in some scenarios (e.g. full imports vs. delta imports) to leverage the progress bar idea for the Event Broker console.

Answer
anonymous 2 years ago

To be investigated during UI rewrite.

+1
Completed

Preferred DC list for AD agents

Bob Bradley 4 years ago updated by anonymous 3 years ago 10

The native AD MA for the FIM Sync service has long had an optional configuration section for preferred DCs, so that administrators can nominate an ordered list of preferred DCs to connect to for imports/exports. When this is used with Event Broker, especially in forests where there are delays in AD replication between DCs, the result can be that Event Broker detects a change before it is replicated to the DC from which FIM is connecting. This generally results in a missed change.


A feature to configure the AD agent exactly in line with that in the corresponding AD MA is suggested here.

0

Support for Group Managed Service Accounts (gMSA)

Bob Bradley 2 weeks ago updated 1 week ago 1

Microsoft has just published this MIM article which explains how to configure the MIM Sync and Server service accounts to be gMSA (ones that don't require passwords).

To make for a more compelling business case to leverage this at MIM sites it would help if UNIFYNow (and UNIFYBroker for that matter) also supported gMSA.  This would help simplify MIM/Broker deployments at customer sites.

Can we please have this feature request put forward for consideration?

0
Not a bug

Cannot create sub components within an operations list

Hayden Gray 3 months ago updated by Matthew Davis (Engineering Manager) 3 months ago 1

Hello,


After a recent upgrade to UNIFYNow 3 days ago, after this the service was working fine for some time and confirmed last night still working as expected. Though this morning when attempting to create sub operations (i.e check operation/schedule/listen operation/operation) I get presented with the following error:

Unify.Framework.UnifyCommunicationException: The service client does not implement the IEventServiceClient type.
at Unify.Framework.Web.UnifyController.GetClient[TServiceClient]() in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web\Extensions\UnifyController.cs:line 59
at Unify.EventBroker.Web.OperationController.<.ctor>b__103_1(UnifySiteMapNode node, UnifySiteNodeAttribute attribute, RequestContext context, IDictionary`2 dynamicValues, RouteData data, NameValueCollection postData, NameValueCollection queryString) in C:\agent\_work\86\s\Source\Unify.EventBroker.Web\Controllers\OperationController.cs:line 307
at Unify.Framework.Web.UnifySiteMapProvider`2.UpdateNodeForRequest(TNode node, TNodeAttribute nodeAttribute, RequestContext requestContext, IDictionary`2 dynamicValues, RouteData routeData, NameValueCollection postedData, NameValueCollection queryString) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapProvider.cs:line 150
at Unify.Framework.Web.UnifySiteMapDynamicTree`2.UpdateParentForRequest(TNode parentNode, RequestContext globalRequestContext, IDictionary`2 dynamicValues, RouteData& childRouteData, NameValueCollection& childPostData, NameValueCollection& childQueryString, MethodInfo& childAction, UpdateNode`2 updateNode) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapDynamicTree.cs:line 291
at Unify.Framework.Web.UnifySiteMapDynamicTree`2.FindNodeAndUpdateBranch(HttpRequest request, UpdateNode`2 updateNode) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapDynamicTree.cs:line 222
at System.Web.SiteMapProvider.FindSiteMapNode(HttpContext context)
at System.Web.SiteMapProvider.get_CurrentNode()
at Unify.Framework.Web.UnifySiteMapExtensions.DecorateForm(HtmlHelper htmlHelper, Func`1 form, String submitText, String formId, String title, String name) in C:\agent\_work\69\s\Source\Web\Unify.Framework.Web.SiteMap\UnifySiteMapExtensions.cs:line 50
at ASP._Page_Views_Operation_CreatePlugInOperation_cshtml.Execute() in c:\Program Files\UNIFY Solutions\Event Broker\Web\Views\Operation\CreatePlugInOperation.cshtml:line 16
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
at System.Web.Mvc.WebViewPage.ExecutePageHierarchy()
at System.Web.WebPages.StartPage.ExecutePageHierarchy()
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
at System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass1e.b__1b(IAsyncResult asyncResult)

There are no additional logs produced in the application log or the even viewer logs.

The version of UNIFYNow is v4.0.4. I have checked the other environments and they are not affected by the issues. Any help is greatly appreciated.

Thanks

Answer

IIS was likely caching the object or page, and causing issues. An IIS reset has solved the problem.

0
Not a bug

UNIFYNow logo rendered incorrectly in IE11

Bob Bradley 3 months ago updated 3 months ago 2

The UNIFYNow logo and label is not resizing correctly in IE.

Answer

IIS setup not loading external dependencies correctly, in this case CSS files. Logo displays correctly using the inbuilt web server. Investigation required to determine incorrect IIS configuration.