How to save last login date of user in version 12.0.13

Robin Sch

For a current project using Axon Ivy version 12.0.13, we need to retrieve the date of a user’s last login.

In version 13.1.0 or higher, this information is available out of the box.

Is there any way to access or replicate this functionality in version 12.0.13?

Louis Müller

Unfortunately, we cannot introduce this API in version 12. Therefore, before v13, I would recommend using the "SessionExtension" approach and saving the login data yourself. For more information about SessionExtension, please see https://answers.axonivy.com/questions/3871/logging-last-login-of-a-user.html

Robin Sch

Thank you for your response. I have created a SessionExtension and added it to a plug-in project. The only issue I am facing is that I have to start the plug-in manually each time I launch my test engine.

Is there a way to have the plug-in start automatically when the engine starts?

Louis Müller

I assume you've followed the recommendations under https://answers.axonivy.com/questions/2477/how-to-register-my-code-that-runs-on-every-engine-startup.html. These instructions are probably outdated. I would follow the documentation about the eclipse plugin under https://dev.axonivy.com/doc/12.0/en/concepts/3rd-party-integration/process-extensions.html#axon-ivy-extensions-bundles-eclipse-plugin

For the sake of simplicity, I would try adding your session extension via program start instead of using eclipse plugin. See https://dev.axonivy.com/doc/12.0/en/designer-guide/process-modeling/process-elements/program-start.html

Implement your own program start event bean, where you add and remove your sessions extension.

public class SessionExtensionBean extends AbstractProcessStartEventBean {
	
	@Override
	public void start() throws ServiceException {
		add(sessionExtension)
		super.start();
	}
	
	@Override
	public void stop() throws ServiceException {
		remove(sessionExtension)
		super.stop();
	}
}

Reference your bean from a program start process element.

mhoffmann

I think it might be easier to just override the login processes from the Portal (if applicable to you) - there you can simply add a script step after a successful authentication which might be easier to maintain across updates.