Shulou(Shulou.com)06/02 Report--

Environmental Background:

1. The operating system can log in normally;

2. Weblogic console password forgotten (or new management task taken over), unable to log in;

Solution: Add a new administrative user, log in to console and then modify the password of the old user.

3. Solution steps:

3.1. Back up the boot.properties file and the DefaultAuthenticatorInit.ldift file. When the latter operation cannot be realized, it can also be restored. The specific path is based on the Weblogic installation directory. If it is not found, you can use search to find it (linux uses the find command). Example: Take Windows Server 2008 R2+ LOGY 10.3.6 default installation as an example: C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\security\boot.properties

C:\Oracle\Middleware\user_projects\domains\base_domain\security\DefaultAuthenticatorInit.ldift

3.2. Stop Weblogic 3.3. Please make sure that java of this machine can be used. If environment variables are not set or not installed, java that comes with <$Language installation can also be used, as shown in the following figure.

Use the command line to execute cd C:\Oracle\Middleware\jdk160_29\bin and go to the java directory that comes with it, and execute the following command

Java -cp C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar weblogic.security.utils.AdminAccount admin admin .

This command is to create a DefaultAuthenticatorInit.ldift file, which is generated in the current directory by default, as shown below:

(Note that there is a dot at the end, there is a space before the dot, not the same as the original)

Generate a DefaultAuthenticatorInit.ldift file from the current directory, overwriting the C:\Oracle\Middleware\user_projects\domains\base_domain\security\DefaultAuthenticatorInit.ldift file.

3.4. delete

C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\security\boot.properties

C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\data\ldap\DefaultAuthenticatormyrealmInit.initialized

Delete the DefaultAuthenticatormyrealmInit.initialized and boot.properties files. The specific path is based on the Weblogic installation directory. If you can't find it, you can use search (linux with find command).

3.5. Start Weblogic in the foreground, you need to enter the user name and password used to start, the user name is admin, the password is admin can start correctly.

3.6. Log in to the admin console with the new username and password, click "myrealm" in the "security domain," find the previous user in the user and group, modify the password, save it, and then you can continue to log in with the original username.

3.7. User name and password need to be entered every time you restart. You can create a new boot.properties. The user password is the user name and password (plaintext) that have just been modified. The format is

username= username

password= password

3.8. Restart Weblogic application, now do not need to enter the user name and password, after successful launch, weblogic will encrypt the user password, so that you can log in with the old user, the new administrative user can be deleted.

3.9. Password cracking is now complete (pro-test valid).

Written on Tuesday, November 3, 2015 by Liu Yongchun

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.