chris21 accounts left open at AHG

AHG supplied screen shot of logged on users.

I did foresee this issue arising and raised my concerns with Frontier at time of development. The default setting for this type of login will timeout after about 3 minutes, and hence was never considered an issue.

AHG appear to be using a different setting, to possibly never timeout the logged in user, leaving them logged in indefinitely.

I will check to see if there is a way to log out the current user after each call, although I can foresee that this will also cause issues also, so I need to ensure that this mechanism works for both AHG (the indefinite logged in user), and the current method of letting the user timeout. This may require a setting in the configuration.

My last concern is priority of this issue. Have AHG actually purchased this connector yet?

I will also update the estimated time for the issue.

Assigning to Anton, priority needs to be defined.

AHG has purchased and deployed Identity Broker for chris21 v3.0.5.

E-mail from Deanna March dmarch@ahg.com.au:

Hi Shane,

I'm not sure if Doug has passed this on to you yet but I thought I'd throw it your way just in case.

We have noticed that the scheduled Unify process seems to be leaving behind open logins in Chris21 and were wondering whether you might know why this is?

By the way, thanks for your help so far, I feel like we have some momentum again!

Cheers
Deanna

Sent to AHG in response:

Deanna,

I’m sorry that a response had not been sent your way, as looking at our issue tracking system the question was raised and answered by the Identity Broker for Frontier chris21 lead developer/architect.

His response was:

Rodney Pullini added a comment - 19/Jan/11 6:37 PM
I did foresee this issue arising and raised my concerns with Frontier at time of development. The default setting for this type of login will timeout after about 3 minutes, and hence was never considered an issue.
AHG appear to be using a different setting, to possibly never timeout the logged in user, leaving them logged in indefinitely.
I will check to see if there is a way to log out the current user after each call, although I can foresee that this will also cause issues also, so I need to ensure that this mechanism works for both AHG (the indefinite logged in user), and the current method of letting the user timeout. This may require a setting in the configuration.

Do you know if any configuration change has been made for this? If not, I will see if Rodney has any further comment and whether this should be raised with Frontier.

Thank you for bringing this to my attention, and you’re welcome with regards to finding a resolution to the current issues.

Thanks,

Shane

Response from Deanna March dmarch@ahg.com.au:

Hi Shane,

Thanks for your prompt response!

I'll follow up with the Chris21 experts here and see what our current settings are on that front.
I'll be in touch shortly....

Thanks,
De

Shane L,

I have found the required GTR request required to log-off a user:

GTR,token:cbr="logoff"

This will require a new version. There will be an extra configuration item skipLogout="False" needed for this action to take place. The default will be skipLogout="False", to mimic current behaviour use skipLogout="True".

Once the development change is complete, I will give you an installer for acceptance testing.

In the mean time, I suggest the client sets the chris21 user to time-out, or periodically clear the redundant logged-in users.

Received from Deanna March dmarch@ahg.com.au:

Hi Shane,

James and Joel have just been going through the doco and checking the various Chris21 settings and apparently there is a scheduled process that runs every day in production which clears any logins left behind. Usually the act of closing the client properly clears this, but, obviously, we don't have a client in this situation.

It turns out that process isn't running in our test environment which is why they have been building up. So, in short, it will not be a problem for production so we can close this one!

Thanks again!

Cheers
De

Response to Deanna:

Hi Deanna,

I’m glad to hear that is the case and I have fed this back to Rodney.

Thank you for letting me know the outcome.

Shane

I have already done the change, so it will exist in the next release anyway.

This fix is included in UNIFY Identity Broker for Frontier chris21 v3.0.5.2.

A new configuration item is available call skipLogout. The skipLogout attribute defaults to False, which means that by default the logout routine will be called, which differs from earlier behaviour. Set skipLogout="True" to mimic earlier behaviour, where the user timed out instead of logging out.

Shane L,

Please confirm this issue is fixed by performing user acceptance testing.

Hi Rodney,

Could you please help to clarify for me please.

The new configuration for chris21 to fix the logoff issue is to add the skipLogout attribute as True or False to the communicator element, eg

          <communicator logActive="True" gtrForm="pdt" gtrName="Test" gtrPassword="test" skipLogout="False" gtrLogOff="True" gtrAllowHttp="True" gtrShowTranslations="True" gtrListRequest="Default" gtrChunkSize="2000" gtrEaiFile="PSDET" gtrEaiKey="Full" httpUri="https://w2k3r2-chris21/Scalable/c21connect.asp" encoding="UTF-8" contentType="application/x-www-form-urlencoded" />

I assume that the initially proposed attribute, gtrLogOff is not use.

In any case, I installed Identity Broker for chris21 v3.0.5.2 and have tried configuration using both attributes above and the Identity Broker service can start up fine.

However, when I perform the following I encountered the following errors:

1. Terminated a user in chris21
   
2. "Synchronise Import" on the Termination connector result in the following error:

   Starting deletion of chris21 GTR EAI change files.",Verbose
   20110202,06:35:06,chris21 GTR EAI Communicator,Poll,Information,Completed successfully after [00:00:00.2500000] duration.,Verbose
   20110202,06:35:06,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Relationship Connector.,Normal
   20110202,06:35:06,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Relationship Connector reported 0 changes. Duration: 00:00:00,Normal
   20110202,06:35:06,Change detection engine poll completed.,Change detection engine,Information,Change detection engine poll for connector Chris21 Relationship Connector returned 0 possible changes. Duration: 00:00:00.9218750,Normal
   20110202,06:35:06,Change detection engine poll started.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector started.,Normal
   20110202,06:35:07,chris21 GTR EAI Communicator,Poll,Information,Started successfully.,Verbose
   20110202,06:35:07,chris21 GTR EAI Communicator,Poll,Information,"Completed polling successfully after [00:00:00.1093750] duration.
   
   getEaiFile=EMTER;getEaiKey=Number
   
   Starting deletion of chris21 GTR EAI change files.",Verbose
   20110202,06:35:07,chris21 GTR EAI Communicator,Poll,Information,Completed successfully after [00:00:00.1093750] duration.,Verbose
   20110202,06:35:07,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal
   20110202,06:35:07,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Termination Connector reported 0 changes. Duration: 00:00:00,Normal
   20110202,06:35:08,Change detection engine poll completed.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector returned 0 possible changes. Duration: 00:00:01.0937500,Normal
   20110202,06:35:08,Change detection engine poll started.,Change detection engine,Information,Change detection engine poll for connector Chris21 Placement Connector started.,Normal
   20110202,06:35:08,chris21 GTR EAI Communicator,Poll,Information,Started successfully.,Verbose
   20110202,06:35:08,chris21 GTR EAI Communicator,Poll,Information,"Completed polling successfully after [00:00:00.1718750] duration.
   
   getEaiFile=EMPOS;getEaiKey=NumberDate
   
   Starting deletion of chris21 GTR EAI change files.",Verbose
   20110202,06:35:08,chris21 GTR EAI Communicator,Poll,Information,Completed successfully after [00:00:00.1718750] duration.,Verbose
   20110202,06:35:08,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Placement Connector.,Normal
   20110202,06:35:08,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Placement Connector reported 0 changes. Duration: 00:00:00,Normal
   20110202,06:35:08,Change detection engine poll completed.,Change detection engine,Information,Change detection engine poll for connector Chris21 Placement Connector returned 0 possible changes. Duration: 00:00:00.9218750,Normal
   20110202,23:22:22,Logging Engine,Logging Engine,Information,Log file started.,Minimal
   20110202,23:22:22,Change detection engine poll started.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector started.,Normal
   20110202,23:22:22,chris21 GTR EAI Communicator,Poll,Information,Started successfully.,Verbose
   20110202,23:22:41,chris21 GTR EAI Communicator,Poll,Information,"Completed polling successfully after [00:00:18.7500000] duration.
   
   getEaiFile=EMTER;getEaiKey=Number
   Key:Count=1;detnumber=102966
   
   Starting deletion of chris21 GTR EAI change files.",Verbose
   20110202,23:22:41,chris21 GTR EAI Communicator,Poll,Error,"Exception occured after [00:00:18.9062500] duration.
   
   System.ArgumentNullException: Value cannot be null.
   Parameter name: token
      at Unify.Framework.Chris21GtrDataLine..ctor(String token)
      at Unify.Framework.Chris21GtrDataLineFromChris21GtrStringConverter.Transform(String sourceValue)
      at Unify.Framework.Chris21GtrWorker.GetChris21GtrRecordFromStream(Stream gtrStream)
      at Unify.Communicators.Chris21GtrEaiCommunicatorBase.Poll(IMultiKey`1 schemaKey)",Verbose
   20110202,23:22:41,Change detection engine poll failed.,Change detection engine,Warning,"Change detection engine poll for connector Chris21 Termination Connector failed with reason Value cannot be null.
   Parameter name: token. Duration: 00:00:19.1250000
   Error details:
   System.ArgumentNullException: Value cannot be null.
   Parameter name: token
      at Unify.Framework.Chris21GtrDataLine..ctor(String token)
      at Unify.Framework.Chris21GtrDataLineFromChris21GtrStringConverter.Transform(String sourceValue)
      at Unify.Framework.Chris21GtrWorker.GetChris21GtrRecordFromStream(Stream gtrStream)
      at Unify.Communicators.Chris21GtrEaiCommunicatorBase.Poll(IMultiKey`1 schemaKey)
      at Unify.Connectors.Chris21GtrEaiConnectorBase`1.PollChanges(IStoredValueCollection changeState)
      at Unify.Framework.ConnectorToPollingConnectorBridge.PollChanges(IStoredValueCollection changeState)
      at Unify.Framework.EventNotifierPollingConnectorDecorator.PollChanges(IStoredValueCollection changeState)
      at Unify.Framework.ChangeDetectionPollJob.RunBase()
      at Unify.Framework.MutexJobDecorator.Run()
      at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
      at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
   

Reverting the configuration to a known working version still result in the same error.

Performing "Full Import" also resulting in the same error above.

Please see log file attached for additional information. IdB configuration files also attached.

IdB configuration files for chris21 and the log file that contains the errors.

Assign to Rodney for help.

Shane L,

I can't replicate this error. Please list the steps to recreate, and more importnantly the steps to recreate it failing on a full import.

Thanks

This is fixed, new UNIFY Identity Broker for Frontier chris21 v3.0.5.2 installer at:

https://unifysolutions.jira.com/wiki/display/SUBIDBCHRS/Downloads

The configuration item used is skipLogout="True|False". It will default to skipLogout="False", which means the logout routine will be called by default. To mimic earlier behaviour (pre v3.0.5.2) then set skipLogout="True" and then logout routine will not be called.

Also, if an error occurs in the logout routine, then it will now appear as a warning in the log file, and normal operation will continue.

Hi Rodney,

I performed upgrade from IdB for chris21 v3.0.5 to IdB for chris21 v3.0.5.2 (uninstall old version and install new version).

Restart IdB Service without making any configuration change at all.

Run "Synchronise Import" on chris21 Termination connector (I know there is outstanding delta change on chris21 system for termination details).

I got the following warning message that "command is not valid" in the log file.

20110203,23:05:47,Logging Engine,Logging Engine,Information,Log file started.,Minimal
20110203,23:05:46,Change detection engine poll started.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector started.,Normal
20110203,23:05:47,chris21 GTR EAI Communicator,Poll,Information,Started successfully.,Verbose
20110203,23:06:04,chris21 GTR EAI Communicator,Poll,Information,"Completed polling successfully after [00:00:17.3125000] duration.

getEaiFile=EMTER;getEaiKey=Number

Starting deletion of chris21 GTR EAI change files.",Verbose
20110203,23:06:04,chris21 GTR EAI Communicator,Poll,Warning,"Logout failed with the following message:

GTR line type is recognized but not valid [Command].",Verbose
20110203,23:06:04,chris21 GTR EAI Communicator,Poll,Information,Completed successfully after [00:00:17.3281250] duration.,Verbose
20110203,23:06:04,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal
20110203,23:06:04,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Termination Connector reported 0 changes. Duration: 00:00:00,Normal
20110203,23:06:04,Change detection engine poll completed.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector returned 0 possible changes. Duration: 00:00:17.6250000,Normal

I am not sure what this mean. I assume that the logout command is not successfully.

Reopened and assign for assessing the information provided.

This is now available for testing.

Test with the latest Identity Broker for chris21 v3.0.5.2 download

Verified that the skipLogout="True" and skipLogout="False" configuration as part of <communicator> chris21 as per updated documentation Frontier+chris21+connector

The following verification is performed:

• Can start the Identity Broker service successfully
• Can perform "Full Import" on various chris21 Connectors (Person, Address, Placement, Termination etc) successfully
• Can perform "Synchronise Import" on various chris21 Connectors (Person, Address, Placement, Termination etc) successfully

Issue resolved and verified. Closed.