weblogic change password & password reset

1, After the Console changes the password, the attached service cannot be restarted [solution]

1. Open the weblogic console, the security realm -- > myrealm -- > users and groups, and you will see the weblogic users. You can delete them directly or click weblogic to modify them. Save here and it will take effect immediately.

2. An error will be reported when the weblogic console is restarted. You can see the following prompt information through cmd.

<2015-6-27 01:02:27 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>  
<2015-6-27 01:02:27 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>  
<2015-6-27 01:02:27 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>  
#This is because the user name and password used to start the service are the same as those logged in, and the boot The password in the properties file is still old.

3. So you need to modify the domain_ Home/servers/server_ Name/security/boot Properties file, change the username and password to the new password in clear text, and each server must change it.

4. Then restart the managed server and the management server. Boot The contents of the properties file have been changed to ciphertext.

II weblogic console login password forgotten [solution]

1. First, enter the weblogic installation directory and back up three files: boot Properties, defaultauthenticatorinit Ldift, defaultauthenticatormyralminit Initialized.

2. Regenerate a new defaultauthenticatorinit Ldift file. The specific operations are as follows:

#Find weblogic Jar path

#In%domain_ Execute the following command under home%/security:
java -classpath /data/bea/weblogic11/wlserver_10.3/server/lib/weblogic.jar weblogic.security.utils.AdminAccount weblogic weblogic123 .

#jar can be a relative path or an absolute path; Weblogic Security Utils Adminaccount fixed format; Weblogic is the user name, weblogic123 is the password, and a space and a dot are added at the end Last one Don't forget)

#After execution, a new defaultauthenticatorinit will be generated under the current path Ldift file.

3. Create a new boot Properties file, and write: username=weblogic password=weblogic123 to save.

4. Delete the ldap folder under XX/servers/AdminServer/data/,

5. Restart weblogic and delete the backup boot Properties, defaultauthenticatorinit Ldift, defaultauthenticatormyralminit Initialized three files.

III Supplementary description of problems

Failed to start weblogic after account / password modification. I encountered two situations The error difference is from: <notice> <security> <bea-090082> <security initializing using security realm myrealm.> Statement

3.1 When passed/ Startmanagedweblogic When sh is started, enter the wrong password manually and print the log as follows:

Suppose that the account / password has been changed from weblogic/weblogic123 to weblogic/weblogic798, and the password is intentionally entered as wbwbwb wb

[weblogic@localhost bin]$ ./startManagedWebLogic.sh httpserver http://localhost:7001
.
.
JAVA Memory arguments: -Xms256m -Xmx512m  -XX:MaxPermSize=128m
.
WLS Start Mode=Production
.
CLASSPATH=/home/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/Oracle/Middleware/jdk160_29/lib/tools.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/weblogic/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/weblogic/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/weblogic/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:.:/home/rootbobo/data/jdk/jdk1.7.0_80/lib/dt.jar:/home/rootbobo/data/jdk/jdk1.7.0_80/lib/tools.jar
.
PATH=/home/weblogic/Oracle/Middleware/wlserver_10.3/server/bin:/home/weblogic/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/home/weblogic/Oracle/Middleware/jdk160_29/jre/bin:/home/weblogic/Oracle/Middleware/jdk160_29/bin:/home/rootbobo/data/jdk/jdk1.7.0_80/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/weblogic/bin
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) Server VM (build 20.4-b02, mixed mode)
Starting WLS with line:
/home/weblogic/Oracle/Middleware/jdk160_29/bin/java -server   -Xms256m -Xmx512m  -XX:MaxPermSize=128m -Dweblogic.Name=httpserver -Djava.security.policy=/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy  -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/cacerts   -da -Dplatform.home=/home/weblogic/Oracle/Middleware/wlserver_10.3 -Dwls.home=/home/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/home/weblogic/Oracle/Middleware/wlserver_10.3/server   -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001  -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/home/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/home/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath  weblogic.Server
<2017-5-18 04:35:50 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true> 
<2017-5-18 04:35:50 PM CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true> 
<2017-5-18 04:35:51 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 20.4-b02 from Sun Microsystems Inc.> 
<2017-5-18 04:35:52 PM CST> <Info> <Security> <BEA-090065> <Getting boot identity from user.> 
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<2017-5-18 04:35:59 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 > 
<2017-5-18 04:36:01 PM CST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001.> 
<2017-5-18 04:36:01 PM CST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.> 
<2017-5-18 04:36:01 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<2017-5-18 04:36:01 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> 
<2017-5-18 04:36:01 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/httpserver/logs/httpserver.log is opened. All server side log events will be written to this file.> 
<2017-5-18 04:36:04 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.> 
<2017-5-18 04:36:04 PM CST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied> 
<2017-5-18 04:36:04 PM CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied
        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        Truncated. see log file for complete stacktrace
> 
<2017-5-18 04:36:04 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> 
<2017-5-18 04:36:04 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> 
<2017-5-18 04:36:04 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> 
[weblogic@localhost bin]$

If this is the problem, use the correct user name and password to start it again

3.2 Mistaken for boot Properties configuration error, actually nodemanager SH password problem

This error usually occurs when nodemanager SH will report when starting the managed Server

[weblogic@localhost bin]$ ./startWebLogic.sh 
.
.
JAVA Memory arguments: -Xms256m -Xmx512m  -XX:MaxPermSize=128m
.
WLS Start Mode=Production
.
CLASSPATH=/home/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/Oracle/Middleware/jdk160_29/lib/tools.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/weblogic/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/weblogic/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/weblogic/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:.:/home/rootbobo/data/jdk/jdk1.7.0_80/lib/dt.jar:/home/rootbobo/data/jdk/jdk1.7.0_80/lib/tools.jar
.
PATH=/home/weblogic/Oracle/Middleware/wlserver_10.3/server/bin:/home/weblogic/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/home/weblogic/Oracle/Middleware/jdk160_29/jre/bin:/home/weblogic/Oracle/Middleware/jdk160_29/bin:/home/rootbobo/data/jdk/jdk1.7.0_80/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/weblogic/bin
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) Server VM (build 20.4-b02, mixed mode)
Starting WLS with line:
/home/weblogic/Oracle/Middleware/jdk160_29/bin/java -server   -Xms256m -Xmx512m  -XX:MaxPermSize=128m -Dweblogic.Name=AdminServer -Djava.security.policy=/home/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy  -Dweblogic.ProductionModeEnabled=true   -da -Dplatform.home=/home/weblogic/Oracle/Middleware/wlserver_10.3 -Dwls.home=/home/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/home/weblogic/Oracle/Middleware/wlserver_10.3/server   -Dweblogic.management.discover=true  -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/home/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/home/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath  weblogic.Server
<2017-5-18 05:03:53 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true> 
<2017-5-18 05:03:53 PM CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true> 
<2017-5-18 05:03:54 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 20.4-b02 from Sun Microsystems Inc.> 
<2017-5-18 05:03:55 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 > 
<2017-5-18 05:03:56 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<2017-5-18 05:03:56 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> 
<2017-5-18 05:03:56 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.> 
<2017-5-18 05:04:00 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.> 
<2017-5-18 05:04:00 PM CST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.> 
<2017-5-18 05:04:00 PM CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied
        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        Truncated. see log file for complete stacktrace
> 
<2017-5-18 05:04:00 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> 
<2017-5-18 05:04:00 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> 
<2017-5-18 05:04:00 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Cause analysis:
In fact, we have changed the AdminServer management console password at this time, but NodeManager still remembers the old password. When using NodeManager to start the managed Server, you do not need to read the boot Properties, only in use/ Startmanagerweblogic The boot Properties account password

Solution:
1. You need to enter wlst(weblogic script tool) to let NodeManager crawl the configuration of AdminServer again

#Please execute the following commands sentence by sentence
cd /data/weblogic/wls/wlserver_10.3/common/bin

sh ./wlst.sh 

connect('weblogic','password123','t3://ip:7004')

nmEnroll('/data/weblogic/servers/m95/')

disconnect()

exit()

2. After execution, restart NodeManager

3. The console starts under the managed Server

Note: if the same error is reported here It doesn't matter. Go to the managed server directory and clear the cache

cd /oracle/esbapp/bea/weblogic11/user_projects/domains/esb_domain/servers/vhlSearch/
rm -rf tmp
rm -rf stage/
rm -rf cache/
rm -rf data

reference

https://blog.csdn.net/nayan8664/article/details/81330086
nmEnroll explanation: Reference https://my.oschina.net/psuyun/blog/145595#OSC_h2_1 Search nmEnroll

Tags: Middleware

Posted by Hobgoblin11 on Wed, 01 Jun 2022 00:35:55 +0530

Hot Tags

©2023 Programs Team