All you are doing is changing the logon for Admin, to be a different name, there is no issue with this that I have ever seen.

You're right Toby.Prince but I already found in some tomcat logs some entries referring to "Admin" login which was missing.

That's why I was asking that.

I was not aware any part of the system explicitly looked at usernames, as opposed to user IDs, that is interesting.

I suppose the only way to be sure is to run this on a test.

As I said, I have never been made aware of any issues with renaming the admin username, and neither have I ever been warned not to. I have seen many customer sites using the admin logon that has been renamed, and have not come across any issues.

I would be very interested to know if Tomcat is looking for a name at any point.

Hi,

It should be fine. Everything's matched up using the user_userid column rather than user_logon. It's possible that the error in the Tomcat logs was being raised owing to the absence of an admin logon (in the general sense), or because the admin username was specified somewhere in a config file (most likely in the Swiftpage syncengine.properties).

Thanks,

Rob

Thank you for your comment Rob, I will check that asap.

There is no special user called admin, all users created including admin profile users are considered as licensed users and hence changing them to any specific name would not cause any issues. In case you are referring to the name of the log files relevant to the tomcat logs then it would have no impact on your renaming it to root or even manager.