WebLogic stopManagedWeblogic.sh script requests a username and password to disable a managed server

Question

A managed server created in WebLogic 12c asks for a username and password when the managed server stops with the stopManagedWeblogic.sh script, even if the boot.properties file is present with the correct credentials.

The boot.properties file is configured in another accessible location, the path of which is specified using the -Dweblogic.system.BootIdentityFile java option

I observed below strange behavior

• It does not ask for a username and password when starting a managed server with a startManagedWeblogic.sh script (I assume this is in the boot.properties file).
• It does not ask for a username and password when starting and stopping the admin server

It asks for a username and password only if the managed server shuts down using the stopManagedWeblogic.sh script.

Does server management without a password work in WebLogic ?, since I do not want the username and password to be specified as a parameter to stop the script.

Answer 1

It is identified as a bug in WebLogic 12c

The stopManagedWeblogic.sh implementation stopManagedWeblogic.sh ignores the -Dweblogic.system.BootIdentityFile parameter and checks the boot.properties file inside the location <domain_home>/servers/<managed_server_name>/security/boot.properties , if the boot.properties file is not in this place, it requests credentails Admin Server

Answer 2

I ran into a similar problem and was able to solve it by trying the following:

• create the directory <domain_home> / servers / <managed_server> / security
• create boot.properties in the above directory with the values ​​below:
  username = <username>
  password = <password>
  

Now start / stopManagedWeblogic.sh will work without asking for credentials.

Answer 3

I want to stop the managed WebLogic server without specifying an administrator URL, username and password at run time. /stopmanagedweblogic.sh Is there a way to create a stop script in which we can determine the administrator URL, username and password, and when stopping, we just need to run: ./ stopmanagedweblogic.sh the name of the managed server.