WLS Admin User ***** is not permitted to boot the server

Problemas de acesso ao WLS Admin Console do ETPM server

Admin server error: User ***** is not permitted to boot the server

********* Trecho do log abaixo ************
<Aug 5, 2014 9:10:35 AM CAT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0  Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Aug 5, 2014 9:10:35 AM CAT> <Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>
<Aug 5, 2014 9:10:37 AM CAT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 5, 2014 9:10:37 AM CAT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 5, 2014 9:10:37 AM CAT> <Notice> <Log Management> <BEA-170019> <The server log file /u01/app/etpm/PROD11/logs/system/myserver.log is opened. All server side log events will be written to this file.>
<Aug 5, 2014 9:10:38 AM CAT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 5, 2014 9:10:38 AM CAT> <Critical> <Security> <BEA-090404> <User system is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
<Aug 5, 2014 9:10:38 AM CAT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User system is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User system is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1009)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Aug 5, 2014 9:10:38 AM CAT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 5, 2014 9:10:38 AM CAT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 5, 2014 9:10:38 AM CAT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
++ set +x

**************************************

Solução:

1 - Verificar se o utilizador system não está cadastrado em mais de um provedor, ou seja, no provedor embutido (ou Default Provider) do weblogic e num outro externo (Ex: OpenDS, Base de Dados, etc).

2 - Caso o utilizador system esteja no provedor externo e no embutido certifique se não tem a mesma senha de login nos dois provedores... é recomendável que a senha utilizada pelo utilizador system no provedor externo seja diferente da utilizada pelo system no provedor embutido  (ou Default Provider) do weblogic.

3 - Elimine o utilizador system do provedor externo e reinicialize o weblogic... caso este levante com sucesso, confirma-se que o system do provedor externo tinha a mesma senha utilizada pelo system no Default Provider.

4 - Teste o login no Admin Console e verifica se o resultado é positivo.

5 - Cadastre o utilizador system no provedor externo alterando a senha de acesso para uma diferente da utilizada pelo system no provedor embutido, ou seja, no Default Provider.

6 - Volte a baixar e levantar o weblogic e, verifique se o servidor levanta sem erros.

7 - Faz o teste de login no Admin Console com a senha do system do provedor embutido.

Boa sorte