#311 Use system user name for logon rather than user management

[Terry O'Neill]

It would be good to allow DPR to be set up to simply use the system user.name for logging on rather than handling its own user management. The way this should work is that when running DPR it would simply automatically log on without any password using the system user.name property. On the database side this would actually create an entry in the database dpr_user table if one does not exist or otherwise set the user to an entry that it finds. This would retain correct audit trail information while making the system much easier to administer and use. Note that as before security would be based on the system logon rather than on DPR. This method would still require some input from users to add in details of the user (i.e. their name).

[Terry O'Neill]

Fixed on version_6.1_fixes branch and assigned to Kirti to test.

Now when a user starts DPR it simply logs in to the set database using the system user.name. If there is no user in the database for this then it will ask for the First Name and Surname of the user. These can also be set from the Actions menu. This change also removes the log out action and the Users menu. The old settings can be reverted by adding a preference behind the scenes but I have not created a option in the program to add this preference (this preference is user.management.enabled=true for au.gov.naa.digipres.dpr.ui.core).

Logging in as a different user can be done using the -Duser.name=<name> option to the Java Virtual Machine.</name>

If automatic logon cannot be done because of connection errors or missing preferences for the connection then the normal logon details screen will be shown.

If a user is set with active=false then an exception will be thrown when attempting to start DPR and thus automatically logon.

[Terry O'Neill]

Was removed from version 6.1.0 release. Now should be tested for version 6.2.0 release in ver_6_2 branch.