Users are disabled the morning of there last working day and we need them to only be disabled +1 day of there last working day.

Currently can not read the CRM schema via CRM connector.

When attempting to pull down the CRM schema i receive the following error: Unable to load the embedded resource 'Unify.Service.Embedded.Microsoft.Xrm.Sdk.dll' from Unify.Service.Connect, Version=4.0.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4:

HALP!

We are seeing this error in our IdB logs. We are unsure why or where it is coming from

20150611,22:13:57,UNIFY Identity Broker,Adapter engine,Error,"Request to get the transformed configuration of the adapter engine.
Request to get the transformed configuration of the adapter engine errored with message: Exception has been thrown by the target of an invocation.. Duration: 00:00:00.4304601
Error details:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Unify.Framework.UnifyEngineException: Composite adapters do not have their own context. Each composite adapter consists of multiple adapters which maintain their own contexts.
at Unify.Product.IdentityBroker.CompositeAdapter.get_Context()
at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.get_Context()
— End of inner exception stack trace —
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[] index)
at Unify.Framework.Configuration.ConfigurationToXmlAdapter.SerializeObject(XElement parentNode, Object item, Int32 recursion)
at Unify.Framework.Configuration.ConfigurationToXmlAdapter.SerializeValue(XElement propertyElement, IEnumerable enumerableValue, Int32 recursion)
at Unify.Framework.Configuration.ConfigurationToXmlAdapter.SerializeObject(XElement parentNode, Object item, Int32 recursion)
at Unify.Framework.Configuration.ConfigurationToXmlAdapter.Transform(Object sourceValue)
at Unify.Framework.Configuration.ConfigurationToTransformationAdapter.Transform(IConfigurationTransformationParameter sourceValue)
at Unify.Framework.Configuration.ConfigurationTransformationGenerator.RetrieveDefaultTransformedConfiguration(Object configuration)
at Unify.Framework.Configuration.ConfigurationEngineBase.RetrieveDefaultTransformedConfiguration(Object configuration)
at Unify.Framework.Configuration.ConfigurationEngineNotifierDecorator.RetrieveDefaultTransformedConfiguration(Object configuration)
at Unify.Framework.Configuration.ConfigurationEngineAccessor.RetrieveDefaultTransformedConfiguration(Object configuration)
at Unify.Product.IdentityBroker.AdapterEngine.RetrieveTransformedAdapterConfiguration()
at Unify.Product.IdentityBroker.AdapterEngineNotifierDecorator.RetrieveTransformedAdapterConfiguration()
at Unify.Product.IdentityBroker.AdapterEngineAccessor.RetrieveTransformedAdapterConfiguration()
at Unify.Product.IdentityBroker.IdentityServiceCollector.RetrieveDefaultTransformedAdapterConfiguration()
at SyncInvokeRetrieveDefaultTransformedAdapterConfiguration(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.ProcessMessage41(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)",Normal

The Configure Adapter Screen - Distinguished Name Template doesnt respond well to input & its not obvious how it should work.

The default DN is:
CN=key

If I delete the key, so it just says:
CN=

No suggestions appear underneath the text box via AJAX. Its only when you delete the whole line & wait that something appears. This is not very user friendly.

Also, typing makes it lose where it's up to, so the next time a component is clicked the component is added in a strange place.

The current implementation does not allow for multiple template editors to be on the same page due to the use of html id's. If possible make use of random id's to allow for multiple dn template editors on the one page.

Do we have any examples of provisioning to Broker if the object has a multi-part DN (eg: UID=<object>,OU=users). Currently I'm getting an error in that OU=users does not exist. Has this been done? Proven not to work?

When viewing logs in IdB, sometimes want to go to last page and then scroll back a page at a time. To do this, we click on the previous button/link at the bottom of the page. When the log contains multi-line items, that link/button moves on the screen, so it is not possible to hold the mouse in one place and repeatedly click. If the page number links and previous/next links could be at the top of the list they would remain in one place making this scrolling easier.
Thanks
#first world problem
#lazy consultant

Edit: Look at adding the scrollbar as well, as this can be hidden with large amounts of data.

On startup the following error is displayed:

Unify.Framework.UnifyServiceInitializeException: The given key was not present i
n the dictionary. ---> System.Collections.Generic.KeyNotFoundException: The give
n key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Unify.Product.IdentityBroker.AgentEngine.InitializeFromXml(XDocument xml)
   at Unify.Framework.UnifyEngine`1.Initialize()
   --- End of inner exception stack trace ---
   at Unify.Framework.UnifyEngine`1.Initialize()
   at Unify.Service.Connect.Debug.ProgramProxy.Execute()

The error is a result of the connector not having been installed. Consider a better message to be displayed to users.

Unable to set the time offset transformation with "days". Able to only set hour,min,seconds.

See attached screenshot

The CSODBB student solution uses a "SAS2IDM" branded instance of the SQL Connector (IdB 3.*) to present consolidated student records to FIM in a read-only manner. The data is a consolidated SQL 2008 database managed by a custom "SAS2IDM" application which merges data replicated from 43 schools in the Diocese, which I believe was written for CSODBB by a 3rd party consultant .

I would like to earmark the SAS2IDM application for replacement by a new style of connector designed to connect to each of the 43 school instances directly, allowing consolidation to a single adapter in a "like-for-like" swap out initially, but ultimately to allow write-back to the SAS application (if there's a business case for this). Before we can propose such a model, a feasibility assessment would need to be commissioned either by CSODBB, or by UNIFY as a pre-sales idea.

If you're happy for this to proceed simply to the point of an initial assessment, I have already broached this idea with Shane previously and now with Tony Sheehy. I would like to get this into the sales pipeline for CSODBB down the track, as the value proposition would be in terms of reduced maintenance overhead and superior solution performance. The estimate is therefore just to cover an initial feasibility assessment by someone in the UNIFY PG.

Hi Gents,

I've Started testing the existing SharePoint connector for compatibility with SharePoint 2013.

So far I've installed the 2010 web service into SharePoint and confirmed it's install via the install guide. https://unifysolutions.jira.com/wiki/display/IDBSP40/Installing+the+SharePoint+2010+WCF+Service

I've also installed the connector and performed a successful connection test with the existing agent.

The first issue I've encountered is around the schema discovery components. On attempting scheme discovery, the following error is thrown:

The schema for 'SPTest Connector' connector was not updated for the following reason: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Value cannot be null.
Parameter name: serviceContext (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
System.ArgumentNullException: Value cannot be null.
Parameter name: serviceContext
at Microsoft.Office.Server.UserProfiles.ProfileManagerBase..ctor(SPServiceContext serviceContext)
at Microsoft.Office.Server.UserProfiles.ProfileManagerBase..ctor(SPServiceContext serviceContext, Boolean ignorePrivacy)
at Microsoft.Office.Server.UserProfiles.UserProfileManager..ctor(SPServiceContext serviceContext, Boolean IgnoreUserPrivacy, Boolean backwardCompatible)
at Microsoft.Office.Server.UserProfiles.UserProfileManager..ctor(SPServiceContext serviceContext)
at Unify.Connectors.SharePoint.SharePoint2010WCFService.UNIFYIdentityBrokerService.SharePoint2010UserProfileService.GetSchema()
at SyncInvokeGetSchema(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperation...).

I've discussed this with Shane, and will be submitting a Source Control request for access to the SharePoint connector repository. In the absence of Adam, I will be investigating this and any other issues that arise from integrating with the new version of SharePoint.