InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.18: Securing applications >
6.6.18.3: Administering security with the Web console >
6.6.18.3.6: Specifying user IDs for the server and administrator with the Web console

6.6.18.3.6: Specifying user IDs for the server and administrator with the Web console

Before enabling security, specify an ID and password under which the application server will run:

  1. In the tree on the left side of the console, click Security -> Local OS Authentication to display the authentication settings.
  2. Click the Local OS User Registry link.
  3. On the resulting panel, specify a valid Server ID and Server Password. The user ID-password pair must be defined already in the user registry of the local operating system, and must have "Act as Operating System" privileges (on Windows NT).
  4. Click OK.

You can use the same ID and password to log in to the Web administrative console, or you can set up a different ID and password.

Setting up another user ID for logging in to the Web console

To set it up so that you can log in to the administrative console using an ID and password other than the server ID and password:

  1. Expand the tree on the left side of the console to display Nodes -> hostname -> Enterprise Applications -> Server Administration Application.
  2. In the property sheet for the application, locate and click the Mapping Roles to Users task to display the panel for mapping roles to users.
  3. For the Administrator role, specify values for the users, groups, and other settings. This is where you can specify additional IDs other than the server ID.
  4. When finished changing the settings, click Next to display the confirmation page.
  5. When finished confirming the settings, click Finish. The modifications will be saved to the EAR file for the application.
  6. Save your configuration.
  7. (Optional) To have the configuration take effect:

    1. Stop the server
    2. Start the server again.
Go to previous article: Removing global security with the Web console Go to next article: Avoiding known security risks in the runtime environment

 

 
Go to previous article: Removing global security with the Web console Go to next article: Avoiding known security risks in the runtime environment