Thursday, May 20, 2010
Wednesday, May 19, 2010
Issues while creating weblogic Custom Security Provider
One of the most important and common errors that generally comes while creating the Custom Security Providers is :
om.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for XXXXXX is not specified.
The above error comes due to incorrect usage of the Weblogic Mbean maker.
We should always use the below directory structure for creating the Custom Security Provider for Weblogic Server:
om.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for XXXXXX is not specified.
The above error comes due to incorrect usage of the Weblogic Mbean maker.
We should always use the below directory structure for creating the Custom Security Provider for Weblogic Server:
Wednesday, May 12, 2010
How to resolve : Authentication denied: Boot identity not valid
<11-May-2010 20:00:57 o'clock CEST> <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.>
The above mentioned error occurs generally during server startups:
The above mentioned error occurs generally during server startups:
Tuesday, May 11, 2010
How to debug SSL issues with weblogic server
First of all I would suggest using the following debug flag in case of any kind of SSL issue on Weblogic server:
-Dweblogic.StdoutDebugEnabled=true
-Dssl.debug=true
If you need to debug any SSL issue with the standalone JAVA class then you can use the following debug flag:
-Djavax.net.debug=all : This is for turning all debugging.
-Djavax.net.debug=ssl : This is for turning SSL debugging.
Then In case if you are getting the following exception in the debug trace:
Monday, May 3, 2010
How to Develop Weblogic Custom Audit Provider
Through this post I will be providing the steps to develop a sample custom Weblogic Audit Provider.
Following files are required for this sample tutorial:
SimpleSampleAuditProviderImpl : This is a sample runtime class implementing the AuditProvider and AuditChannel.
SimpleSampleAuditorImpl : This is a sample class that extends the ContextHandlerImpl class to get the supported ActiveContextHandlerEntries
SimpleSampleAuditor : This is a sample Audit configuration Mbean Configuration file used to instantiate the Custome Audit Provider Mbean Type.
We will be following the link give below:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/dvspisec/aud.html
Following files are required for this sample tutorial:
SimpleSampleAuditProviderImpl : This is a sample runtime class implementing the AuditProvider and AuditChannel.
SimpleSampleAuditorImpl : This is a sample class that extends the ContextHandlerImpl class to get the supported ActiveContextHandlerEntries
SimpleSampleAuditor : This is a sample Audit configuration Mbean Configuration file used to instantiate the Custome Audit Provider Mbean Type.
We will be following the link give below:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/dvspisec/aud.html
Subscribe to:
Posts (Atom)