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.
Upgrade from Identity Broker for chris21 v3.0.5 to 3.0.5.2
Perform upgrade of Identity Broker for chris21 from v3.0.5 to 3.0.5.2 (by uninstalling older version and install the newer version).
Make no change to any of the Identity Broker's Connector and Adapter configuration for chris21.
Restart Identity Broker service successully.
Performed "Clear All..."
Performed "Import All Connectors..." result in the following errors for all Connectors for chris21.
20110203,23:18:56,Adapter clear started.,Adapter,Information,Adapter d5251d7d-05cc-4d35-916e-e99e06b9ffd3 clear started.,Normal 20110203,23:18:58,Adapter clear completed.,Adapter,Information,Adapter d5251d7d-05cc-4d35-916e-e99e06b9ffd3 clear completed in duration 00:00:02.7343750.,Normal 20110203,23:19:27,Change detection engine import all items started.,Change detection engine,Information,Change detection engine import all items for connector Chris21 Person Connector started.,Normal 20110203,23:19:27,Chris21 Person Connector,GetAllEntities,Information,Started successfully.,Verbose 20110203,23:19:27,chris21 GTR EAI Communicator,List,Information,Started successfully.,Verbose 20110203,23:19:28,chris21 GTR EAI Communicator,List,Warning,"Logout failed with the following message: GTR line type is recognized but not valid [Command].",Verbose 20110203,23:19:28,chris21 GTR EAI Communicator,List,Information,Completed successfully after [00:00:00.0468750] duration.,Verbose 20110203,23:19:28,Chris21 Person Connector,GetAllEntities,Information,Completed successfully after [00:00:00.0468750] duration.,Verbose 20110203,23:19:28,Request to get all entities from connector.,Connector,Information,Request to get all entities from connector Chris21 Person Connector.,Normal 20110203,23:19:28,chris21 GTR EAI Communicator,List,Information,Chunking [2000] is implemented after [00:00:00.0468750] duration.,Verbose 20110203,23:19:28,Get all entities from connector failed.,Connector,Warning,"Get all entities from connector Chris21 Person Connector failed with reason GTR line type is recognized but not valid [Command].. Duration: 00:00:00.0156250 Error details: System.IO.InvalidDataException: GTR line type is recognized but not valid [Command]. at Unify.Framework.Chris21GtrWorker.ExtractListResult(ICollection`1 entities, IChris21GtrRecord record, Int32 entityKeyCount) at Unify.Communicators.Chris21GtrCommunicatorBase.<ListWithChunking>d__0.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnFirst>d__1c`1.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.ActionOnExceptionEnumerator`1.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnLast>d__16`1.MoveNext() at Unify.Framework.EnumerableExtensions.<ProduceAutoPages>d__9`1.MoveNext() at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit() at Unify.Framework.Visitor.VisitEvaluateOnThreadPool[T](IEnumerable`1 visitCollection, Action`2 visitor, Int32 maxThreads) at Unify.Framework.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities) at Unify.Framework.ChangeDetectionImportAllJob.ImportAllChangeProcess() at Unify.Framework.ChangeDetectionImportAllJob.RunBase() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
Is there any other configuration that I may need to update or change?
AdapterEngine.extensibility.config.xml
ConnectorEngine.extensibility.config.xml
UnifyLog20110203.csv
Identity Broker for chris21 downgrade stop Identity Broker service from starting
Post upgrade of Identity Broker for chris21 from version 3.0.5 to 3.0.5.2
I ran into the issue that I cannot perform "Synchronisation Import" or "Full Import" on any exist chris21 Connectors. See end of issue IDBCHRS-13 for details of the error.
Since I need my Lab environment for other work for chris21 I downgrade Identity Broker for chris21 back to version 3.0.5. This is done by uninstalling Identity Broker for chris21 v3.0.5.2 and install Identity Broker for chris21 v3.0.5.
I also restore to Connector and Adapter configuration file to the known working ones.
When starting the Identity Broker service I encounter the following error:
Unify.Framework.UnifyServerInitializeException: Could not load file or assembly 'Unify.Framework.LogWorker.Interfaces, Version=3.0.5.0, Culture=neutral, PublicK eyToken=84b9288cb2633de4' or one of its dependencies. The located assembly's man ifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly ' Unify.Framework.LogWorker.Interfaces, Version=3.0.5.0, Culture=neutral, PublicKe yToken=84b9288cb2633de4' or one of its dependencies. The located assembly's mani fest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Unify.Framework.LogWorker.Interfaces, Version=3.0.5.0, Culture=neutr al, PublicKeyToken=84b9288cb2633de4' at Unify.Connectors.Chris21GtrConnectorFactoryBase`3.CreateComponent(IMultiKe yedConnectorFactoryInformation factoryInformation) at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factory Information) at Unify.Framework.ConnectorEngineConnectorGenerator.CreateComponent(IMultiKe yedConnectorFactoryInformation factoryInformation) at Unify.Framework.ConnectorGenerator.CreateComponent(IConnectorGeneratorInfo rmation factoryInformation) at Unify.Framework.PollingConnectorEngineConfigurationFactory.CreateConnector ConfigurationBase(XElement xmlConfiguration, IConnectorHelper connectorHelper, I Timing pollingTiming, INotificationMessageService messageService, ITiming getAll EntitiesTiming, IConnectorGroup connectorGroup) at Unify.Framework.PollingConnectorConfigurationFactoryBase`2.CreateComponent (IConnectorConfigurationFactoryInformation`1 factoryInformation) at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factory Information) at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfi gurationFromNode(THelper connectorHelper, XElement connectorNode, TConnectorConf igurationCollection connectorConfigurationCollection, IConnectorGroup connectorG roup) at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfi gurationCollection(XElement xmlCollection, THelper connectorHelper) at Unify.Framework.ConnectorEngine.Initialize() at Unify.Framework.UnifyEngine.Initialize() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\M icrosoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure lo gging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus ion!EnableLog]. --- End of inner exception stack trace --- at Unify.Framework.UnifyEngine.Initialize() at Unify.Services.Connect.Debug.ProgramProxy.Execute()
I thought that the core files are somehow wrong version thus I uninstall Identity Broker Service v3.0.5.6 and re-install it. The problem persist.
Any advise or assistant on how to resolve this issue would be much appreciated.
Thank you.
Feature request - ability to update non-primary work address
Add the ability to update non-primary work address. The type of address should be configurable if possible, otherwise hard-code to work address. It should be the non-primary address.
The rules in Workday will ensure that there is only one address that satisfies these conditions.
Add ability to request multiple employee status types
Allow the employee connector to request more than one employee status type.
EmployeeID/joining changes
We expected this but confirmed due to Aurion Corp's feedback:
- EmployeeID will not always be an option and we need to allow for an alternative field to contain the Aurion PersonNumber
- Regardless of where it comes from, the field may sometimes be empty or duplicated which means it's not appropriate for use in the DN
Review LITE terminology
Not all that surprising, but feedback from Aurion Corp is that some of the terminology (mostly identity-related stuff) is difficult to understand. We've already been through a few revisions of it but we should find some time to do it again, maybe with a neutral 3rd party.
Edit Synchronization Settings Potential Updates.png
Synchronization Page Potential Updates.png
Adding an entity which fails validation leaves an entry in the LDAP entity cache
Adding an entity via the LDAP endpoint which fails schema validation leaves an entry in the entity cache with the requested DN. This means that a second attempt to add the entity that should succeed will instead fail saying the entity already exists. Consider any other conditions that might result in a non-existing entity remaining in the entity cache and verify that they are handled correctly.
SapHR Test Harness Issues
A new version of the test harness was provided to us for testing this solution, version is 3.0.1.
I've extracted the archive and run the executable. The executable is not in the Identity Broker directory.
I get an error regarding missing DLLs
System.IO.FileNotFoundException: Could not load file or assembly 'SAP.Connector.Rfc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' or one of its dependencies. The system cannot find the file specified. File name: 'SAP.Connector.Rfc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(AssemblyName assemblyRef) at SAP.Connector.RfcConnectorLoader.LoadRfcConnector() at SAP.Connector.RfcConnectorLoader.GetRfcConnection(IDestination dest) at SAP.Connector.Connection.GetNewConnection(IDestination dest) at SAP.Connector.Connection.GetConnection(IDestination dest) at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 451 at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
To try to get around this, I copied the missing DLL (there are two) from the Identity Broker service directory, but I then get the error
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) at SAP.Connector.Connection.Open() at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 455 at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58
Event log error
Fault bucket , type 0 Event Name: PCA2 Response: Not available Cab Id: 0 Problem signature: P1: Unify.TestHarness.SapHrCommunicator.exe P2: 3.0.1.3 P3: Unify.TestHarness.SapHrCommunicator P4: UNIFY Identity Broker for SAP HCM P5: UNIFY Solutions Pty Ltd P6: 200 P7: -1 P8: P9: P10: Attached files: These files may be available here: C:\Users\a16716.TESTINTERNAL\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_Unify.TestHarnes_18e927a83648e251bb989378285ab8f6680a1e1_2d5cb42b Analysis symbol: Rechecking for solution: 0 Report Id: 2076e8d0-3f55-11e2-8a8f-005056ba0004 Report Status: 4
SAP timing configuration for IdB 3.*
The following is the timing configuration for one of 10 connectors defined in the IdB 2.* solution currently in Production:
<getAllEntities> <timing name="RecurringTimespan"> <timespan value="3600000000" /> </timing> </getAllEntities> <polling> <timing name="RecurringTimespan"> <timespan value="3600000000" /> </timing> </polling>
... i.e. reading this literally, both full AND delta every 6 minutes!!!
I had converted the above to the following for IdB 3.* - mainly for readability:
<getAllEntities> <timing name="Daily" offset="21:00:00" /> </getAllEntities> <polling> <timing name="RecurringTimespanStandardTime"> <timespan value="00:10:00" /> </timing> </polling>
... on the basis that it seemed silly to have both nodes set at the same frequency. I have been happily testing with this for the last couple of days ... but had started to notice that polling wasn't working .
I had not noticed the "delta import" button on the UNIFY Management Studio 3.* toolbar before Friday, but when I click on this for the above IdB 3.* connector configuration I get the following error in the IdB log:
Timestamp Severity Source Module Message 8/04/2013 1:49:57 PM Warning Change detection engine poll failed. Change detection engine "Change detection engine poll for connector Organisational Structure Connector failed with reason The connector 7d7e4969-2a73-4669-848c-67cb72c7867c does not support polling.. Duration: 00:00:00.0361342 Error details: System.NotSupportedException: The connector 7d7e4969-2a73-4669-848c-67cb72c7867c does not support polling. at Unify.Framework.ConnectorToPollingConnectorBridge.get_PollingConnector() at Unify.Framework.ConnectorToPollingConnectorBridge.PollChanges(IStoredValueCollection changeState) at Unify.Framework.EventNotifierPollingConnectorDecorator.PollChanges(IStoredValueCollection changeState) at Unify.Framework.ChangeDetectionPollJob.RunBase() at Unify.Framework.JobBase.Run() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)"
I then went looking in the JIRA doco for this connector, including here, but couldn't find any doco about whether or not this connector should support polling.
Is the Production configuration wrong but nobody has ever noticed? It is consistent with version 2.4 of the spec which says the following:
15.2 Identity Broker
Connector Event Timespan Description
SAP HCM GetAllEntities 3600000000
SAP HCM Polling 3600000000
I suspect the SAP HCM connector has somehow never been a polling connector ... but I just wanted to make sure!
Simple way to test aurion connectivity for Identity Broker
Identity Broker needs to keep a connection open to Aurion for an extended period of time and we can have problems with proxies and firewalls cutting the connection. Is there something we can give to the network guys at a customer to prove to them where the connection is being cut? I am thinking either a test they could do themselves that keeps the connection open for the right length of time and in the right way, or some kind of network diagnostic we could run from the IB server.
Customer support service by UserEcho
