Upgrade the configuration engine to allow for:

• Individual configurations to be retrieved/applied.
• Make configuration engine use application storage;
• Migration code from install directory to application storage;
• All configuration files to be retrieved/applied - possibly zip them up?
• Endpoint methods to allow for UI integration;
• UI for configuring settings and retrieving/applying configuration.

See https://unifysolutions.jira.com/wiki/pages/viewpage.action?pageId=41320640 for further details.

Trying to do a full import on multiple SAP connectors in 64bit mode..

Change detection engine import all items for connector sapOrgUnit failed with reason The request channel timed out while waiting for a reply after 00:00:59.9960936. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.. Duration: 00:01:00.1614898

Updates to the MOSS List connector are failing. I have attempted to update the Author and the Description field. Error message:

See screenshot for attempted modification.

In order to assist in the configuration of larger amounts of connectors and adapters, a copy function should be added. Consider being able to create multiple copies of a connector and adapter.

Tony has already done the method on the service for connectors, method will need to be added for the adapter engine.

Please also allow for copy to csv and copy to placeholder. Possibly even copy to any other type.

In future versions, some smarter options for configuring multiple connectors and adapters may be considered, such as a mass configuration wizard.

The validation message for the illegal DN template of:

CN=Surname,FirstName,DC=organization

Is not descriptive of the problem, namely:

System.Core:
System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
at Unify.Product.IdentityBroker.TemplateDistinguishedNameCompiler`2.ComponentGenerate(TemplateDistinguishedNameComponent component)
at Unify.Product.IdentityBroker.TemplateDistinguishedNameCompiler`2.CreateComponent(IList`1 factoryInformation)
at System.Linq.Enumerable.<>c__DisplayClass12`3.<CombineSelectors>b__11(TSource x)
at System.Linq.Enumerable.<>c__DisplayClass12`3.<CombineSelectors>b__11(TSource x)
at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Unify.Framework.IO.DistinguishedName.GetStringValue()
at Unify.Product.IdentityBroker.Repository.EntityDistinguishedNameMultiValueDataUtility`1.ConvertValueToString(DistinguishedNameValue value)
at Unify.Product.IdentityBroker.Repository.StringBasedMultiValueDataUtilityBase`3.GetEntityValue(__EntityValueInsertRow entityValue, TBaseValue baseValue)
at Unify.Product.IdentityBroker.Repository.EntityMultiValueDataUtilityBase`3.<>c__DisplayClass1.<CreateEntityValue>b__0(TBaseValue baseValue, Int32 index)
at System.Linq.Enumerable.<SelectIterator>d__7`2.MoveNext()
at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
at Unify.Framework.Visitor.Visit[T](IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Product.IdentityBroker.Repository.KnownEntityContextBase`4.InsertItems(HashSet`1 addedItems, EntityDataContext sourceContext, SqlConnection connection)
at Unify.Framework.Data.LinqContextConversionBase`4.SubmitChanges()
at Unify.Product.IdentityBroker.Adapter.<>c__DisplayClassf6.<ReflectPage>b__f3()
at Unify.Framework.ParallelGate.ParallelGateJob.RunBase()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)

If an empty gtrSecurePassword attribute is present in a communicator element (ie. gtrSecurePassword=""), the below error message is thrown to the Event Viewer. This error message should be made more specific. The better solution would be to change the method to deal with an empty value.

—

Error occurred in module: Connectors

The following error occurred:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at System.Security.Cryptography.RijndaelManagedTransform.DecryptData(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount, Byte[]& outputBuffer, Int32 outputOffset, PaddingMode paddingMode, Boolean fLast)
at System.Security.Cryptography.RijndaelManagedTransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
at System.Security.Cryptography.CryptoStream.FlushFinalBlock()
at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at System.IO.Stream.Dispose()
at Unify.Framework.SecureStringExtensions.WorkerDecryptString(String encryptedString)
at Unify.Framework.SecureStringExtensions.GetAttributeSecureString(XElement workerInformation, XName attributeName, String defaultValue)
at Unify.Framework.Chris21GtrWorkerFactory.CreateComponent(XElement workerElement)
at Unify.Connectors.Chris21GtrConnectorFactoryBase`3.CreateComponent(IMultiKeyedConnectorFactoryInformation factoryInformation)
at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Framework.ConnectorEngineConnectorGenerator.CreateComponent(IMultiKeyedConnectorFactoryInformation factoryInformation)
at Unify.Framework.ConnectorGenerator.CreateComponent(IConnectorGeneratorInformation factoryInformation)
at Unify.Framework.PollingConnectorEngineConfigurationFactory.CreateConnectorConfigurationBase(XElement xmlConfiguration, IConnectorHelper connectorHelper, ITiming pollingTiming, INotificationMessageService messageService, ITiming getAllEntitiesTiming, IConnectorGroup connectorGroup)
at Unify.Framework.PollingConnectorConfigurationFactoryBase`2.CreateComponent(IConnectorConfigurationFactoryInformation`1 factoryInformation)
at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfigurationFromNode(THelper connectorHelper, XElement connectorNode, TConnectorConfigurationCollection connectorConfigurationCollection, IConnectorGroup connectorGroup)
at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfigurationCollection(XElement xmlCollection, THelper connectorHelper)
at Unify.Framework.ConnectorEngine.Initialize()
at Unify.Framework.UnifyEngine.Initialize()

A string surrounded by double quotes written to csv

"text"

get written to the file as

""text""

and imported back into the connector as the first.

This string

<Email address="aaagu3@domain.com" />

gets written to the csv with double quotes

<Email address=""aaagu3@domain.com"" />

however when imported back to the connector the double quotes persist.

Due to IDB-799, the schema retrieval for MOSS List and 2007 User Profile does not work:

As a workaround, the connector factories should call CreateComponent to recreate the connector in the schema retrieval rather than relying on the connector repository.

As per our discussion - the SharePoint2010UserProfileConnector and 2007 User Profile connector requires an account field to be the first key for ModifyAnchor to work.

A determination should be made about whether the AccountName field in SharePoint can change, and if so whether the current field name can be retrieved.

This raises a question about the concrete requirements for a fixed schema in a larger sense, and what a fixed schema is event meant to be.

There are a number of ways of potentially thinking about fixed schemas:

e.g.

• A fixed schema field is a field that cannot be changed from a concrete/constant field defined in IDB
• A fixed schema field is a field that must be present, and needs to be requested from the target identity management store.
• A fixed schema field is a field which must be a key or must have a name, or must be readonly etc., but all other values can change
• A fixed schema field is there to help, and that takes precedence over whether it doesn't necessarily need to be in the schema (but will always be in the target store).

etc. etc.

The Chris21ListRequest enumerable allows for the handling of "Specific" list requests, denoted by the value "S" being sent to Chris21. This seems to mean that only fields present in the schema will be returned. The connector currently throws a "not supported" exception in the case where the connector is configured in this way.

"Default" and "All" type retrieval are used in current Chris21 configurations without any issues, so this is a minor issue to revisited at some stage. Until then, it may be worth commenting the "Specific" type out of the enumerable so it is not selectable via the UI.

Estimate includes updating the connector to support specific handling and testing.