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()

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.

New c21 users do not have their position populated in ILM until VERY late in their lifecycle (sporadic population of position data). As a result users do not have any associated position information / manager details etc at provision time.

I have not seen this at any other client site.

Example User
Employee ID: 1200210

RAW GTR:

cbr="detlst",gw_transactionid="17",detnumber="1200210",dettitle="MR",detsurname="Mazereeuw",detdatejnd="2012-12-03",
detg1name1="Martin",detg1name2,detprefnm,detpresurn,dettele,detbirdate="1967-04-17",detmarcd,detemailad,detterdate,
detntid,dettempdt2,dettempdte,detsubpos="OTA012",detalttele,updatetag="MORROWE ;21127140110",accesslevel="add",status="ok" 

C21 Org Unit Connector imports all position information correctly

C21 Placement Connector provides the correct reference between posnumber and employeeID/detNumber

C21 Employee ADAPTER does NOT show associated position information for the new user - This occurs WEEKS later

I originally thought there was an error with the relationship processing in the adapter configuration within idB. All connector information seems to be available for the relationship to occur, although the adapter does not present the information with the relationships intact...

This is very strange as the transformations seem to be correct for all existing users RE position information - It just seems to be processed at a later date regardless of if the information is available in identity broker..

I will post the adapter config tonight

HALP!

Both AHG and GCCC have plans to upgrade to chris21 v7.5 in the not too distant future. It appears that in the extensive release notes for that version, it is mentioned that some database tables have been changed. Given the current issues at AHG, they have specifically asked us to confirm whether that upgrade will require changes to the Identity Broker solution.

Gold Coast City Council has asked whether an upgrade of Oracle from Version 9 to either 10g or 11g will have any impact on Identity Broker for chris21. It is presumed that there is NO associated upgrade to the chris21 application version.

The error from Chris21 is passed straight through to the IdB UI and displays the password.
I don't think this is desirable.

Enable the connector to fetch the names of available Chris21 forms on configuration. We could use the scripted dropdown control so that it does not become cumbersome to navigate the hundreds of forms available by default.

Estimate includes restructuring the UI for the required multi-step approach, and research into how to retrieve form details via GTR.

From SSICT-493, a certain condition was causing the chris21 service to return a PRG GTR line. This had not been seen before, but the details can be found on INTIDBCHRS:v7.7 Documentation, in CHRIS_BRE_SDK.pdf.

Essentially PRG is a progress message, why it's being returned is currently unknown, but it doesn't matter, it (and any other unknown line types) should be ignored.

From discussions on TATTS-7, allow for images to be saved and retrieved.

Please see attached demo code.

Either create a test application for POC, or add it straight to the product if you feel it will be quicker.

Thanks.

It seems if a form has its EAI disabled, simply enable EAI will not allow connector to detect changes from it.
Steps I took to make connector to be able to detect changes:
1. Restart Chris21 service. (as a result, connector is not able to detect changes)
2. Restart IdB service. (as a result, connector is not able to detect changes)
3. Do a "Import all" and then modify some data in CHRIS21. (as a result, connector is able to detect changes)