Running Business Processes and Composite Applications 10.4 | Running Business Processes and Composite Applications | webMethods Integration Server Administrator’s Guide | Managing Users and Groups | Disabling and Enabling User Accounts
 
Disabling and Enabling User Accounts
 
Disabling a User Account
Enabling a User Account
There may be times when you need to disable a user account. Doing so makes password cracking attacks harder by eliminating well-known user names. When you disable a user account, login attempts with that user name will fail authentication and be rejected. For example, you might disable the user account of a developer who is on vacation, or the account of a trading partner whose trading privileges are suspended. Because the user has been disabled rather than deleted, you can later reinstate the account without changing the password or resetting permissions.
For deployment, you should disable the Administrator user to prevent someone from trying to guess the password and gain access to your system. Before disabling the Administrator user, you must first create another user, for example SmithAdmin, and add it to the Administrators, Developers, and Replicators groups. Then disable the Administrator user. (Internal server functions that run as the Administrator user, such as start up and shut down services, will still be able to run as Administrator.) Then you can use the SmithAdmin user to administer your Integration Server.

Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release