OTN Home > Oracle WebLogic Server 10.3.6.0 Documentation > Administration Console Online Help > Configure Windows NT security realms

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure Windows NT security realms


To configure the Windows NT security realm:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane, expand Compatibility Security > Realms and click New.

    The Create a New Basic Realm page appears.
  3. In the Name field, enter a name for the Windows NT security realm.
  4. In the Type drop-down list, select NT Realm and click OK.
  5. Configure the Caching realm.

    For more information, see Configure Caching realms.

    When configuring the Caching realm, select your Windows NT security realm from the pull-down menu for the Basic Realm attribute on the Caching Realms: Configuration: General page. The Basic Realm attribute defines the association between the Caching realm and the alternate security realm (in this case, the Windows NT security realm).

  6. In the left pane, select your domain (for example, mydomain).
  7. Expand Compatibility Security > File Realm.
  8. In the Caching Realm field, select the name of the Caching realm to be used with the Windows NT security realm. A list of configured Caching realms appears on the pull-down menu.
  9. Reboot WebLogic Server.

After you finish

Use the following command to verify that you have the correct privileges to run WebLogic Server as the specified Windows NT user:

java weblogic.security.ntrealm.NTRealm username password

where username and password are the username and password of the Windows NT account under which WebLogic Server runs.

The output from this command indicates whether the specified username and password authenticated properly.
Command Description

auth?poppy

The entered username and password authenticated correctly.

auth?null

The entered username and password did not authenticate properly.
If the test comes up with an immediate failure stating that the client or user running WebLogic Server does not have the privileges to run the Windows NT Security realm,then it may be necessary to do one of two things:
  • Boot the server using -Dweblogic.security.ntrealm.logonNetwork=true to change the NTRealm's NT Logon from LOGON32_LOGIN_INTERACTIVE to LOGON32_LOGIN_NETWORK.
  • Update the permissions (referred to as rights) for the Windows user running WebLogic Server to provide the user with the NT "Log on Locally" user right. See Update user permissions in Windows NT and 2000.

Back to Top