How to execute WebLogic security related commnads?

Hello All
I am just learning Oracle WebLogic and humbly request you for all your help. I installed Oracle WebLogic Server 11g Release 1 (10.3.3) on my Windows XP desktop. I could able create and cluster manage servers, configure WebLogic plug-in to Sun Java Web Server (I installed that on my Windows XP desktop) etc. Now I am reading the documentation about security and wants to run some of the commands as shown below
1) weblogic.security.SSL.protocolVersion (Command-line argument lets you specify which protocol is used for SSL connections)
2) Dweblogic.security.SSL.enableJSSE=true|false (System property to enable and disable JSSE SSL)
I am not sure how to execute this commands. As I cannot execute these commands from the AdminServer console, the only way left is C:\ prompt on my desktop. So I figured out the security directory under C:\Oracle\Middleware\user_projects\domains\Domain1\security on my desktop and tried to execute the commands unsuccessfully from C:\
C:\Oracle\Middleware\user_projects\domains\Domain1\security>weblogic.security.SSL.protocolVersion
'weblogic.security.SSL.protocolVersion' is not recognized as an internal or exte
rnal command,
operable program or batch file.
Where I can execute these commands and your help is very much appreciatecd?
Thanks

Hi,
"weblogic.security.SSL.protocolVersion" is only a System property Not a Executable command. This flag is just to tell the JVM to use which version of SSL implementation. This is a System Property which is needs to be enabled in the JAVA_OPTION part of your JVM/Server startScript.
Like if you are starting WebLogic server then U must apply this System property in the server start Scipt JAVA_OPTION variable:
Edit Apply the "startWebLogic.sh" and then add the following like below:
<font color=maroon> *export JAVA_OPTION="${JAVA_OPTIONS} -Xmx1024m -Xms1024m -Dweblogic.security.SSL.protocolVersion=SSL3"* </font>
Below are the meaning of this flag values.
-Dweblogic.security.SSL.protocolVersion=SSL3—Only SSL V3.0 messages are sent and accepted.
-Dweblogic.security.SSL.protocolVersion=TLS1—Only TLS V1.0 messages are sent and accepted.
-Dweblogic.security.SSL.protocolVersion=ALL—This is the default behavior.
Or Suppose if you want to run some standalone Java Program which Uses SSL and if you want to tell the JVM to use SSL3 implementation then you can do something like this:
*java <font color=red>-Dweblogic.security.SSL.protocolVersion=SSL3</font> HelloWorld*
Thanks
Jay SenSharma
*http://middlewaremagic.com/weblogic (Middleware Magic Is Here)*

Similar Messages

  • How to add weblogic portal related plugins to my IDE

    Hi friends,
    I am new to weblogic portal 10.3,How to add wlp 10.3. related functionality to my Eclipse IDE .Can you please provide the suitable plugins to work with wlportal 10.3.
    thanks,
    krishna kolla.

    Hi Pramod,
    You can try this workaround for this:
    Create a DC of type ext library (If already done, then put a Build Time Dependency. Also add all the Jar Files to a Assembly and Complation Public part)
    Create a J2EE Application project and define the dependency on the Ext Lib project *Assembly
    An ear gets generated that you can deploy on your server.
    You need to define a Runtime dependency to this J2EE project in your project where you want to use the jar files.
    This way you can proceed with the development and later on chage the reference when you get the proper method to do so.
    Hope this helps!!
    Cheers,
    Arafat

  • Security related information in SOAP thruough BPEL

    Hi all,
    How to pass the security related information in SOAP(UsernameToken) in BPEL
    thanks
    kalyan

    You can also add the username and password as properties to the invoke .
    open the bpel.xml of your bpel process and the below properties where your partner link is defined
    <property name="wsseHeaders">credentials</property>
    <property name="wsseUsername">YOUR USER</property>
    <property name="wssePassword">YOUR PASSWORD</property>
    As an example check this :
    <partnerLinkBinding name="PartnerLink_1">
    <property name="wsdlLocation">DMSBODServiceRef.wsdl</property>
    <property name="wsseHeaders">credentials</property>
    <property name="wsseUsername">marattu</property>
    <property name="wssePassword">wipro@143</property>
    </partnerLinkBinding>

  • How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

    Dear All,
    I have one statement int weblogic 5.1 weblogic.propertis as follow,
    weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
    but after converting to weblogic 6.1 there are no corresponding statement in
    the file config.xml. And when i start the new application, error occured.
    what should I do?
    The error message is:
    <2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
    .\config\tbcn\config.xml
    <2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initializatio
    Throwable: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Dear Satya,
    My weblogic propertis file as follow,
    # CORE PROPERTIES
    # You should set these before you start the WebLogic Server the first time.
    # If you need more instructions on individual properties in this
    # section, check the same section in the Optional Properties, where
    # we've left the long explanations. Or, better yet, go to our
    # website and read all about properties, at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # CORE SYSTEM PROPERTIES
    # TCP/IP port number at which the WebLogic Server listens for connections
    weblogic.system.listenPort=7001
    # CORE SECURITY-RELATED PROPERTIES
    # Read important information about security at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # REQUIRED: The system password MUST be set in order to start the
    # WebLogic Server. This password is case-sensitive, at least 8 characters.
    # The username for the privileged user is ALWAYS "system".
    # This username and password also includes httpd access (see
    # HTTPD properties below).
    weblogic.password.system=12345678
    # RECOMMEND Set to 'everyone' if HTTPD is enabled
    weblogic.allow.execute.weblogic.servlet=everyone
    # Set individual ACLs to restrict access to HTTP-related resources,
    # such as the Administration servlets.
    # To make your own servlets generally available, follow this
    # pattern (provide a weblogic.allow.execute) for your packages and
    # set ACLs as appropriate.
    # CORE SECURITY-RELATED PROPERTIES FOR SSL
    # Read important information about SSL at:
    # http://www.weblogic.com/docs51/classdocs/API_secure.html
    # Enable SSL
    # (default if property not defined is false)
    weblogic.security.ssl.enable=true
    # SSL listen port
    weblogic.system.SSLListenPort=7002
    # Servlets for SSL
    # Authentication servlet for creating tokens for applets
    weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
    ervlet
    # Limits number of unclaimed stored tokens
    weblogic.security.certificateCacheSize=3
    # Capture CA root of client servlet
    weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
    # Certificates for SSL
    # Name of acceptable CA roots
    # For client authentication change value to a valid .pem file
    #weblogic.security.clientRootCA=SecureServerCA.pem
    # Server certificates for SSL
    weblogic.security.certificate.server=democert.pem
    weblogic.security.key.server=demokey.pem
    weblogic.security.certificate.authority=ca.pem
    # registration for certificate generator servlet
    weblogic.httpd.register.Certificate=utils.certificate
    weblogic.allow.execute.weblogic.servlet.Certificate=system
    # CORE HTTPD ADMINISTRATIVE PROPERTIES
    # True permits the HTTPD to run (default)
    # Uncomment this property to disable HTTPD
    #weblogic.httpd.enable=false
    # If authentication is required, add username/password for each user
    # who will be included in an ACL, as in this commented-out example:
    #weblogic.password.peter=#8gjsL4*
    # SYSTEM PROPERTIES
    # System properties in this section are set to system defaults
    # Performance pack. The shared library must be accessible from your
    # PATH (NT) or from your shared library path (UNIX; the name of the
    # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
    weblogic.system.nativeIO.enable=true
    # Outputs logging information to the console as well as to the log file
    weblogic.system.enableConsole=true
    # Sets the directory or URL for the WebLogic Admin help pages
    # The help pages are shipped in the "docs/adminhelp" directory, in the
    # default document root in public_html
    weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
    # If you prefer to access the most recent help pages, you can do so online
    # by commenting out the previous property and uncommenting this one:
    #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
    # Properties for tuning the server's performance
    # Number of WebLogic Server execute threads.
    weblogic.system.executeThreadCount=15
    # Other optional system properties
    # Limits size of weblogic.log (in K) and versions old log
    weblogic.system.maxLogFileSize=1024
    # Adjust minimum length of password
    weblogic.system.minPasswordLen=8
    # UNIX only: If running on port 80 on UNIX, enable the setUID program
    #weblogic.system.enableSetUID=false
    # UNIX only: Unprivileged user to setUID to after starting up
    # WebLogic Server on port 80
    #weblogic.system.nonPrivUser=nobody
    # CLUSTER-SPECIFIC PROPERTIES
    # Cluster-specific properties in this section are set to system defaults.
    # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
    # in the per-cluster properties file ONLY.
    # Time-to-live (number of hops) for the cluster's multicast messages
    # (default 1, range 1-255).
    #weblogic.cluster.multicastTTL=1
    # Sets the load-balancing algorithm to be used between
    # replicated services if none is specified. If not specified,
    # round-robin is used.
    #weblogic.cluster.defaultLoadAlgorithm=round-robin
    # SERVER-SPECIFIC CLUSTER PROPERTIES
    # Cluster-related properties in this section are set to system defaults.
    # CLUSTER USERS: Note that these server-specific cluster-related properties
    # should be set in the per-server properties file ONLY.
    # Sets the weight of the individual server for the weight-based
    load-balancing.
    # Range is 0 - 100.
    # Larger numbers increase the amount of traffic routed to this server.
    #weblogic.system.weight=100
    # SYSTEM STARTUP FILES - Examples
    # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
    # objects should be registered in the per-server properties file.
    # All other startup classes should be registered in the per-cluster
    # properties file.
    # For more info on writing and using startup file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a startup class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.startupClass.[virtual_name]=[full_pathname]
    # Add arguments for the startup class
    #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/StartupQuery.java
    #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
    #weblogic.system.startupArgs.doquery=\
    # query=select * from emp,\
    # db=jdbc:weblogic:pool:demoPool
    # SYSTEM SHUTDOWN FILES - Examples
    # For more info on writing and using shutdown file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a shutdown class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
    # Add arguments for the shutdown class
    #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/ShutdownTest.java
    #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
    #weblogic.system.shutdownArgs.ShutdownTest=\
    # outfile=c:/temp/shutdown.log
    # SECURITY-RELATED PROPERTIES FOR WORKSPACES
    # For backward compatibility, the following entries disable Access
    # Control on Workspaces
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    # JOLT FOR WEBLOGIC PROPERTIES
    # These properties configure a BEA Jolt connection pool for use with
    # the simpapp and bankapp examples, and register a servlet for use with
    # with the simpapp example. The default server address provided here
    # points to a public TUXEDO server that is hosted by BEA for use with
    # this example.
    # Servlet registration for simpapp example:
    #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
    t
    # Pool creation and cleanup
    # note this example is set up to work with the public
    # demo TUXEDO server available from BEA's website:
    #weblogic.system.startupClass.demojoltpoolStart=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    #weblogic.system.startupArgs.demojoltpoolStart=\
    # poolname=demojoltpool,\
    # appaddrlist=//beademo1.beasys.com:8000,\
    # failoverlist=//beademo1.beasys.com:8000,\
    # minpoolsize=1,\
    # maxpoolsize=3
    #weblogic.system.shutdownClass.demojoltpoolStop=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
    #weblogic.system.shutdownArgs.demojoltpoolStop=\
    # poolname=demojoltpool
    # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
    # The registrations enable a BEA IIOP connection pool and
    # register servlets for use with the simpapp and university examples.
    # Configure for your environment and uncomment to use.
    # Uncommenting these properties requires WebLogic Enterprise Connectivity
    # and an operating WebLogic Enterprise Server.
    # Servlet registration for simpapp servlet example
    #weblogic.httpd.register.SimpappServlet=\
    # examples.wlec.servlets.simpapp.SimpappServlet
    #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
    # Servlet registration for simpapp EJB example
    # (You'll need to add the wlec_ejb_simpapp.jar to the
    # weblogic.ejb.deploy property in this file.)
    #weblogic.httpd.register.ejbSimpappServlet=\
    # examples.wlec.ejb.simpapp.ejbSimpappServlet
    #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
    # Pool creation and cleanup for the simpapp example
    #weblogic.CORBA.connectionPool.simplepool=\
    # appaddrlist=//wlehost:2468,\
    # failoverlist=//wlehost:2468,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # domainname=simpapp
    # Servlet registration for university Servlet example:
    #weblogic.httpd.register.UniversityServlet=\
    # examples.wlec.servlets.university.UniversityServlet
    #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
    # Pool creation and cleanup for the University example:
    #weblogic.CORBA.connectionPool.Univpool=\
    # appaddrlist=//wlehost:2498,\
    # failoverlist=//wlehost:2498,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # apppassword=wlepassword,\
    # domainname=university
    # WEBLOGIC FILE PROPERTIES
    # Maps a volume name to a path, for client file read/write
    #weblogic.io.fileSystem.[volumeName]=[fullPathName]
    # WEBLOGIC JMS DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL JMS deployment should be done in the
    # per-cluster properties file ONLY.
    # You set up a JDBC connection pool if you want persistent messages
    # (including durable subscriptions). To use JMS and EJBs in the same
    # transaction, both must use the same JDBC connection pool. Uncomment
    # the following property to use the default JDBC connection pool
    # 'demo', which is defined in the Demo connection pool section of this file.
    #weblogic.jms.connectionPool=demoPool
    # The JMS Webshare example demonstrates how the ClientID for a
    # durable subscriber is configured in the connection factory:
    #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
    #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
    #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
    #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
    # The JMS trader example shows how to use JMS with an EJB. In addition
    # to uncommenting the following properties, you must also set up and
    # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
    # ejb_basic_statelessSession.jar to try out this JMS example:
    #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
    #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
    #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
    #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
    # Registers the underlying servlet
    #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
    # These properties are used with the ServerReceive JMS example,
    # which demonstrates how to establish a JMS message consumer
    # in a startup class:
    #weblogic.system.startupClass.serverReceive=\
    # examples.jms.startup.ServerReceive
    #weblogic.system.startupArgs.serverReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    # These properties are used with the PoolReceive JMS example,
    # which demonstrates how to establish a pool of JMS message consumers
    # in a startup class:
    #weblogic.system.startupClass.poolReceive=\
    # examples.jms.startup.PoolReceive
    #weblogic.system.startupArgs.poolReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
    # WEBLOGIC RMI DEMO PROPERTIES
    # CLUSTER USERS: Note that pinned RMI objects should be registered
    # in the per-server properties file ONLY. All other RMI startup
    # classes should be registered in the per-cluster properties file.
    # Remote classes registered at startup after the pattern:
    #weblogic.system.startupClass.[virtualName]=[fullPackageName]
    # These examples can be compiled to see RMI in action. Uncomment to use:
    #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
    #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
    #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
    # WEBLOGIC EJB DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL EJB deployment should be done in the
    # per-cluster properties file ONLY.
    # See WebLogic Demo Connection Pool below for a connection pool
    # to use with these examples.
    # Deploys EJBeans. Uncomment the appropriate lines below and
    # modify DBMS-related info and paths to match your particular installation:
    # TBCN EJB PROPERTIES
    weblogic.ejb.deploy=\
    C:/weblogic/myserver/AccountSB.jar, \
    C:/weblogic/myserver/AddressEntryDet.jar, \
    C:/weblogic/myserver/AddressEntry.jar, \
    C:/weblogic/myserver/Affiliate.jar, \
    C:/weblogic/myserver/ContactPerson.jar, \
    C:/weblogic/myserver/ContactSB.jar, \
    C:/weblogic/myserver/Factory.jar, \
    C:/weblogic/myserver/FactorySups.jar, \
    c:/weblogic/myserver/LoginUsers.jar, \
    c:/weblogic/myserver/Member.jar, \
    c:/weblogic/myserver/MemberQuotaUsage.jar,\
    c:/weblogic/myserver/MemberToCategory.jar,\
    c:/weblogic/myserver/Organization.jar, \
    c:/weblogic/myserver/Person.jar, \
    c:/weblogic/myserver/QuotaType.jar,\
    c:/weblogic/myserver/Registration.jar, \
    c:/weblogic/myserver/TempAccounts.jar, \
    c:/weblogic/myserver/TempDomain.jar, \
    c:/weblogic/myserver/UserAccount.jar, \
    c:/weblogic/myserver/UserRole.jar, \
    c:/weblogic/myserver/BuyerProducts.jar, \
    c:/weblogic/myserver/Catalog.jar, \
    c:/weblogic/myserver/Categories.jar, \
    c:/weblogic/myserver/CategoryToCategory.jar, \
    c:/weblogic/myserver/CountryToCategory.jar, \
    c:/weblogic/myserver/InvitedMember.jar, \
    c:/weblogic/myserver/ProductOrigin.jar, \
    c:/weblogic/myserver/ProductOtherFee.jar,\
    c:/weblogic/myserver/ProductSups.jar, \
    c:/weblogic/myserver/Products.jar,\
    c:/weblogic/myserver/ProductToCategory.jar, \
    c:/weblogic/myserver/SecondaryQcEntry.jar, \
    c:/weblogic/myserver/CodeClass.jar,\
    c:/weblogic/myserver/ConfirmationSB.jar, \
    c:/weblogic/myserver/PurchasedPackage.jar,\
    c:/weblogic/myserver/RejectReasonCode.jar, \
    c:/weblogic/myserver/ServiceOrder.jar,\
    c:/weblogic/myserver/ServiceOrderLog.jar,\
    c:/weblogic/myserver/ServiceOrderState.jar,\
    c:/weblogic/myserver/ServiceOrderType.jar,\
    c:/weblogic/myserver/ServicePackageDetails.jar, \
    c:/weblogic/myserver/ServicePackage.jar, \
    c:/weblogic/myserver/ServicePayment.jar, \
    c:/weblogic/myserver/ServiceReqSB.jar, \
    c:/weblogic/myserver/TAM.jar, \
    c:/weblogic/myserver/SubscriptionEB.jar, \
    c:/weblogic/myserver/PostingCategoryEB.jar, \
    c:/weblogic/myserver/PostingBrowsedEB.jar, \
    c:/weblogic/myserver/PostingInfoEB.jar, \
    c:/weblogic/myserver/TransactionLogEB.jar, \
    c:/weblogic/myserver/PostingSB.jar
    #weblogic.ejb.deploy=\
    # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
    # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
    # d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
    # d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
    # d:/weblogic/myserver/ejb_subclass.jar, \
    # d:/weblogic/myserver/jolt_ejb_bankapp.jar
    # Servlet used by the EJB basic beanManaged example
    # Uncomment to use:
    weblogic.httpd.register.beanManaged=\
    examples.ejb.basic.beanManaged.Servlet
    # Add a list of users (set the password with
    weblogic.password.[username]=XXX)
    # to set an ACL for this servlet:
    #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
    #weblogic.password.user1=user1Password
    #weblogic.password.user2=user2Password
    # WEBLOGIC XML DEMO PROPERTIES
    # These properties are required to run the XML examples.
    # Uncomment to use.
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
    # BizTalk example properties
    #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
    #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
    #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
    dapter
    #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
    # WEBLOGIC ZAC DEMO PROPERTIES
    # These registrations enable the ZAC Publish Wizard.
    weblogic.zac.enable=true
    # Set the publish root for a WebLogic Server. Edit and
    # uncomment to use.
    #weblogic.zac.publishRoot=d:/weblogic/zac
    # Set an ACL for each package you publish. The [name] is
    # the "Package name" you assign in the ZAC Publish Wizard.
    # Publish a package, edit this property, and uncomment to use.
    #weblogic.allow.read.weblogic.zac.[name]=[user list]
    #weblogic.allow.write.weblogic.zac.[name]=system
    # HTTPD ADMINISTRATIVE PROPERTIES
    # Enables logging of HTTPD info in common log format and
    # sets the log file name (default is "access.log" in "myserver")
    weblogic.httpd.enableLogFile=true
    weblogic.httpd.logFileName=access.log
    # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
    weblogic.httpd.enableEvents=false
    # Enables HTTP sessions
    weblogic.httpd.session.enable=true
    # Sets an optional cookie name. The default name is "WebLogicSession".
    # Prior to version 4.0, the default was "TengahSession". To make
    # this backward compatible with cookies generated from previous
    # installations, you should set this property to "TengahSession".
    # Uncomment this line and set this to any string of your choice,
    # or comment out this property to use the default.
    #weblogic.httpd.session.cookie.name=WebLogicSession
    # MIME types
    weblogic.httpd.mimeType.text/html=html,htm
    weblogic.httpd.mimeType.image/gif=gif
    weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
    weblogic.httpd.mimeType.application/pdf=pdf
    weblogic.httpd.mimeType.application/zip=zip
    weblogic.httpd.mimeType.application/x-java-vm=class
    weblogic.httpd.mimeType.application/x-java-archive=jar
    weblogic.httpd.mimeType.application/x-java-serialized-object=ser
    weblogic.httpd.mimeType.application/octet-stream=exe
    weblogic.httpd.mimeType.text/vnd.wap.wml=wml
    weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
    weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
    weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
    weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
    # In seconds, the keep-alive for HTTP and HTTPS requests
    weblogic.httpd.http.keepAliveSecs=60
    weblogic.httpd.https.keepAliveSecs=120
    # WEBLOGIC JDBC DRIVER PROPERTIES
    # Enables JDBC driver logging and sets the file name for the log
    # The weblogic.jdbc.logFile is placed in the per-server
    # directory (default is "myserver")
    weblogic.jdbc.enableLogFile=false
    weblogic.jdbc.logFileName=jdbc.log
    # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # For creating JDBC connection pools. This example shows a connection
    # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
    # to use 4 JDBC connections (with a potential for up to 10 connections,
    # incremented by two at a time, with a delay of 1 second between each
    # attempt to connect to the database), to an Oracle database server called
    # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
    # connections are dropped from the pool until only 4 connections remain
    open.
    # Every 10 minutes, any unused connections in the pool are tested and
    # refreshed if they are not viable.
    #weblogic.jdbc.connectionPool.oraclePool=\
    # url=jdbc:weblogic:oracle,\
    # driver=weblogic.jdbc.oci.Driver,\
    # loginDelaySecs=1,\
    # initialCapacity=4,\
    # maxCapacity=10,\
    # capacityIncrement=2,\
    # allowShrinking=true,\
    # shrinkPeriodMins=15,\
    # refreshMinutes=10,\
    # testTable=dual,\
    # props=user=SCOTT;password=tiger;server=DEMO
    # Get more details on each argument for this property in the
    # Administrators Guide on setting properties at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # Set up ACLs for this connection pool with the following:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    # guest,joe,jill
    #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    # This property is an ACL that specifies the users who can
    # create dynamic connection pools:
    #weblogic.jdbc.connectionPoolcreate.admin=joe,jill
    # Read more about setting up and using connection pools in the
    # developers guide for WebLogic JDBC at:
    # http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
    # TBCN JDBC CONNECTION POOL MANAGEMENT
    weblogic.jdbc.connectionPool.oraclePool=\
    url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=tbcn;password=ca91768
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
    weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
    # WEBLOGIC DEMO CONNECTION POOL PROPERTIES
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # This connection pool uses the sample Cloudscape database shipped
    # with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
    # Uncomment to use:
    #weblogic.jdbc.connectionPool.demoPool=\
    # url=jdbc:cloudscape:demo,\
    # driver=COM.cloudscape.core.JDBCDriver,\
    # initialCapacity=1,\
    # maxCapacity=2,\
    # capacityIncrement=1,\
    # props=user=none;password=none;server=none
    # Add a TXDataSource for the connection pool:
    #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
    # Add an ACL for the connection pool:
    #weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
    # WEBLOGIC HTTP SERVLET PROPERTIES
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    # WebLogic offers different types of servlets for various uses.
    # Classpath servlet registration
    # The ClasspathServlet is used to serve classes from
    # the system CLASSPATH. It is used by applets to load
    # classes they depend upon, and is registered against
    # the virtual name 'classes' here by default. This means
    # you should set your applet codebase to "/classes".
    # You can register multiple virtual names for this servlet.
    # Note that it can also be used to serve other
    # resources/files from the system CLASSPATH.
    # Don't confuse the ClasspathServlet with the ServletServlet. The
    # ClasspathServlet is used for serving classes for client-side Java only.
    # The ServletServlet is used to invoke unregistered servlets.
    # See the Administrators Guide "Setting up WebLogic as an HTTP server"
    # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
    info.
    weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
    # We also set an open ACL for everyone to call the ClasspathServlet
    # so that applets work without requiring further changes.
    weblogic.allow.execute.weblogic.servlet.classes=everyone
    # File servlet registration
    # FileServlet searches below the documentRoot for the requested file
    # and serves it if found. If the requested file is a directory,
    # FileServlet will append the defaultFilename to the requested path
    # and serve that file if found.
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    weblogic.httpd.indexFiles=zh_TW/index.htm
    # ServerSideInclude servlet registration
    # SSIServlet searches below the documentRoot for the
    # requested .shtml file and serves it if found.
    weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
    # Example URL: http://localhost:7001/portside/welcome.shtml
    # for the file /weblogic/myserver/public_html/portside/welcome.shtml
    # PageCompileServlet (used by JHTML)
    # See the information below under WebLogic JHTML
    # JSPServlet (used by JSP)
    # See the information below under WebLogic JSP
    # ServletServlet registration
    # Allows unregistered servlets in the servlet classpath (see Servlet
    # reload properties below) to be r

  • How to deploy a secured ADF 11g application to WebLogic 10.3 server?

    Hi,
    I have just enabled security in our ADF 11g application, as descripbed in [chapter 29|http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/adding_security.htm#insertedID0] of the Fusion Developer's Guide. It works fine in the embedded WebLogic server of JDeveloper.
    Now I'm trying to deploy to our WebLogic 10.3 server, which runs in production mode. I'm running into all sorts of problems. The WebLogic console seems to have hundreds of security related pages, I don't know which one I should use, let alone how to use it. The Fusion Developer's Guide doesn't cover deployment to a production server:
    >
    When the target server is configured for production mode, you typically handle the migration task outside of JDeveloper using tools like Oracle Enterprise Manager. For details about using tools outside of JDeveloper to migrate the policy store to the domain-level in a production environment, see the [Oracle Fusion Middleware Security Guide|http://download.oracle.com/docs/cd/E12839_01/core.1111/e10043/toc.htm].
    >
    However, this guide is of very little help to me. I found [chapter 7|http://download.oracle.com/docs/cd/E12839_01/core.1111/e10043/addlsecfea.htm#insertedID0], which says "The recommended tool is Fusion Middleware Control." I have no idea what "Fusion Middleware Control" is, where to get it and how to use it.
    Long story short: I'm totally lost. I'm looking for a step by step guide on how to deploy a secured ADF 11g application to a WegLogic 10.3 server that is running in production mode. Any help is highly appreciated.

    Ok, I found a [very helpful blog post |http://andrejusb.blogspot.com/2009/01/practical-adf-security-deployment-on.html] by [Andrejus Baranovski|http://www.blogger.com/profile/04468230464412457426]. I wish Oracle's documentation was as clear as this...
    The blog post refers to an article by Steve Muench, called [Simplified ADF 11g Application Credential and Policy Migration to Standalone WebLogic Servers|http://www.oracle.com/technology/products/jdev/tips/muench/credmig111100/index.html]. This article presents an Ant script that migrates policies from JDeveloper to WebLogic, using some PFM. (See the last definition here.)
    The problem is that Steve Muench's script assumes that JDeveloper and the standalone WebLogic are on the same machine. However, in a typical environment, such as the one I'm working in currently, this is not the case. In our case the developer stations are Windows machines, while our WebLogic server runs on a HP-UX machine. So the question is: how to perform this migration between two machines with different operating systems?
    Regards,
    Bart Kummel

  • How to create default groups in Weblogic- Security Realms -- Groups

    Hi Team,
    Unfortunately I have deleted some default groups from Weblogic->Security Realms --> Groups. How to add the groups.
    Regards,
    Ravi.

    Hi Ravi,
    These are the defaults groups present inside Security Realms ,you can manually create them by
    Going inside Security Realms-->Users and Groups-->Groups-->New
    Administrators----Administrators can view and modify all resource attributes and start and stop servers-----------------------DefaultAuthenticator
    Deployers---------Deployers can view all resource attributes and deploy applications.---------------------------------------------DefaultAuthenticator
    Monitors-----------Monitors can view and modify all resource attributes and perform operations not restricted by roles.------DefaultAuthenticator
    Operators---------Operators can view and modify all resource attributes and perform server lifecycle operations.-------------DefaultAuthenticator
    Restart the Admin Server
    Regards
    FAbian

  • Testing weblogic server with jdk1.4b3 -- how to configure login security manager?

    Hi got the error I include when trying to start weblogic server sp1 with new jdk1.4b3.
    Since it seems just an error of authentication, I'm wondering if it is possible
    to give a correct login configuration.
    It's just a test to see if we can use jdk1.4 for our next project with Bea Weblogic.
    Thanks,
    pakkio
    D:\bea\wlserver6.0\config\mydomain>notepad startWebLogic.cmd
    D:\bea\wlserver6.0>set PATH=.\bin;d:\apps\Oracle\Ora81\bin;C:\Programmi\Oracle\j
    re\1.1.7\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;d:\apps\Ora
    cle\Ora81\orb\bin;d:\apps\SSH
    D:\bea\wlserver6.0>set CLASSPATH=d:\bea\wlserver6.0.;D:\bea\wlser
    ver6.0\config\mydomain\applications\DefaultWebApp_myserver\WEB-INF\classes\lib\mail.jar;D:\bea\wlserver6.0\config\mydomain\applications\DefaultWebApp_myserver\W
    EB-INF\lib\jasper.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    La sintassi del nome del file, della directory o del volume è incorretta.
    D:\bea\wlserver6.0>"D:\apps\jdk14b3\bin\java" -hotspot -ms64m -mx64m -classpath
    d:\bea\wlserver6.0\ext\crack.jar;.;D:\bea\wlserver6.0\config\mydomain\applicatio
    ns\DefaultWebApp_myserver\WEB-INF\classes\lib\mail.jar;D:\bea\wlserver6.0\config
    \mydomain\applications\DefaultWebApp_myserver\WEB-INF\lib\jasper.jar;.\lib\weblo
    gic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=mydomain -Dweblogic.Name=myserve
    r "-Dbea.home=D:\bea" weblogic.Server
    java.lang.SecurityException: Impossibile trovare una configurazione di login
    at com.sun.security.auth.login.ConfigFile.<init>(ConfigFile.java:99)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
    orAccessorImpl.java:42)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
    onstructorAccessorImpl.java:30)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:277)
    at java.lang.Class.newInstance0(Class.java:301)
    at java.lang.Class.newInstance(Class.java:254)
    at javax.security.auth.login.Configuration$3.run(Configuration.java:223)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.Configuration.getConfiguration(Configuratio
    n.java:217)
    at javax.security.auth.login.LoginContext$1.run(LoginContext.java:172)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.init(LoginContext.java:169)
    at javax.security.auth.login.LoginContext.<init>(LoginContext.java:395)
    at weblogic.security.internal.ServerAuthenticate.main(ServerAuthenticate
    .java:80)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:167)
    at weblogic.Server.main(Server.java:35)
    Caused by: java.io.IOException: Impossibile trovare una configurazione di login
    at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:208)
    at com.sun.security.auth.login.ConfigFile.<init>(ConfigFile.java:97)
    ... 16 more

    Did you find any solution? We have the same problem: If we define a realm in weblogic-application.xml
    <security>
    <!--
    This element names a security realm that will be used by the
    application. If no specified, then the system default realm will be
    used
    -->
    <realm-name>dmzrealm</realm-name>
    </security>
    then the following exception is logged even if there is a dmzrealm in our Weblogic configuration:
    weblogic.security.service.InvalidParameterException: [Security:090396]Security Realm dmzrealm does not exist
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.getSecurityServiceInternal(CommonSecurityServiceManagerDelegateImpl.java:279)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.getSecurityService(CommonSecurityServiceManagerDelegateImpl.java:225)
    at weblogic.security.service.SecurityServiceManager.getSecurityService(SecurityServiceManager.java:188)
    at weblogic.application.internal.flow.SecurityRoleFlow.initSecurityService(SecurityRoleFlow.java:133)
    at weblogic.application.internal.flow.SecurityRoleFlow.prepare(SecurityRoleFlow.java:79)
    Truncated. see log file for complete stacktrace

  • Error in Admin and manager server startup - BEA-149205-  due to error weblogic.security.internal.encryption.EncryptionServiceException

    Hi -
    I have installed OIM 11g r2 ps2, I an tring to start my Admin and SOA server :
    1. Though my admin server is coming up fine, but I am getting the following error when I am trying to start Admin server.
    ####<Apr 22, 2015 12:22:27 AM PDT> <Error> <Deployer> <devoimx003> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
    Kernel>> <> <> <1429687347654> <BEA-149205> <Failed to initialize the application 'opss-DBDS' due to error weblogic.security.internal.encryption.EncryptionServiceException.
    weblogic.security.internal.encryption.EncryptionServiceException
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
            at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
            at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
            at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
            at weblogic.j2ee.descriptor.wl.JDBCDriverParamsBeanImpl.getPassword(JDBCDriverParamsBeanImpl.java:337)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getDriverProperties(DataSourceConnectionPoolConfig.java:368)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$2.run(DataSourceConnectionPoolConfig.java:304)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.initJDBCParameters(DataSourceConnectionPoolConfig.java:300)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.access$000(DataSourceConnectionPoolConfig.java:24)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$1.run(DataSourceConnectionPoolConfig.java:78)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getPoolProperties(DataSourceConnectionPoolConfig.java:75)
            at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)
            at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:176)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:507)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:428)
            at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:280)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
        at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: weblogic.security.internal.encryption.EncryptionServiceException
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
            at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
            at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
            at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
            at weblogic.j2ee.descriptor.wl.JDBCDriverParamsBeanImpl.getPassword(JDBCDriverParamsBeanImpl.java:337)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getDriverProperties(DataSourceConnectionPoolConfig.java:368)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$2.run(DataSourceConnectionPoolConfig.java:304)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.initJDBCParameters(DataSourceConnectionPoolConfig.java:300)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.access$000(DataSourceConnectionPoolConfig.java:24)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$1.run(DataSourceConnectionPoolConfig.java:78)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getPoolProperties(DataSourceConnectionPoolConfig.java:75)
            at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)
            at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:176)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:507)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:428)
            at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:280)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
          at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    2. My SOA server is coming up but in admin mode and giving OPSS connections errors.
    Any help is really appreciated!
    Thanks,
    SK

    Hi Faisal -
    is your domain in development mode or production mode?
         - While configuring my domian , I had selected Prod Mode, but pon start up when I see in admin server console, it is starting in developement mode already ?
    Any idea how, why ?
    if its production mode you can switch to development mode, change all the credentials in the config.xml and configurations under sub folders to cleartext and start the server..
    - Let me still try these and get back to you.
    Thanks,
    SK

  • SOAP handlers and the WebLogic Security Provider Framework

    I am new to WebLogic... I am trying to understand the Weblogic security framework in terms of how a SOAP message would be processed. Do SOAP handlers get called before the configured security providers? after being processed by the Authentication provider? after being processed by the Authorization provider? or at some other point?

    Thanks. But I have some questions about the seed:
    - where is it stored?
    - how is it encrypted?
    - is the seed regenerated periodically? or under certain circumstances?
    Regards,
    Janice Pang
    "Tom Hegadorn" <[email protected]> wrote:
    >
    >
    Hi Janice,
    If you choose to use the PrincipalValidatorImpl class in the
    weblogic.security.provider package, the sign() implementation
    will be the internal weblogic implementation. This implementation
    generates a random seed and computes a digest based on the
    random seed. I hope that helps you.
    Regards,
    Tom Hegadorn
    Sr. Developer Relations Engineer
    BEA Support
    "Janice Pang" <[email protected]> wrote:
    From the online documentations, it is said that this weblogic.security.provider.PrincipalValidatorImpl
    "signs" the authenticated principals to make sure they are not altered
    while they
    are transported on the network.
    The document also mentioned, as a suggested way to develop a customprincipal
    validation provider, to use this class and extend the capabilities of
    user and
    group classes. What kind of private information from the server isused
    for the
    signature and where is that information stored?

  • Weblogic security - acegi

    Hi,
    My application was using acegi security for basic authentication and now I am trying to deploy it under weblogic9.2. I am facing a problem that I need to define the users in weblogic security also to get it authenticated and so browser asks user/password twice, once for weblogic and once for acegi. Can anybody where I might be making mistake.
    My web.xml has this,
         <filter>
              <filter-name>Acegi Filter</filter-name>
              <filter-class>
                   org.acegisecurity.util.FilterToBeanProxy
              </filter-class>
              <init-param>
                   <param-name>targetClass</param-name>
                   <param-value>
                        org.acegisecurity.util.FilterChainProxy
                   </param-value>
              </init-param>
         </filter>
         <filter-mapping>
              <filter-name>Acegi Filter</filter-name>
              <url-pattern>/*</url-pattern>
         </filter-mapping>
    Please inform me about the problem,
    Best regards,
    mik

    There are some information you might be able to find in a SpringOne presentation. It contains the latest information on Spring integration with WebLogic Server, Coherence, and TopLink, respectively. It cites http://www.interface21.com/pitchfork, which contains download links.
    You might also would like to check the following link:
    http://www.oracle.com/technology/tech/java/spring/index.html
    http://www.infoq.com/news/Spring-WebLogic-EJB3
    I am not pretty sure how much it is related to your doubt, however still posting so that those link can be found by anyone browsing for Spring query
    /ed

  • Weblogic security & EJB role based access

    How does (or not) weblogic security tie into the EJB notion of role based
    control ? Can we create a 'custom' security mechanism for EJB (which
    basically uses the EJB facilities but extends it within the application) by
    using custom weblogic realms ?
    Thanks
    Raju

    Thanks !
    "Terry" <[email protected]> wrote in message
    news:[email protected]...
    comments inline
    r <[email protected]> wrote in message
    news:[email protected]...
    >>
    Here are some more specific questions around an 'example' scenario:
    The application has an entity bean 'Account' that can be accessed by the
    roles 'Bank Employee' and 'Customer'
    'Bank Employee' can execute the 'getBalance()' and 'placeOnHold()'
    methods on the 'Account' bean
    'Customer' can execute the 'withdraw()', 'deposit()', and'getBalance()'
    methods on the 'Account' bean
    These permissions are set up through the deployment descriptor by
    mapping
    the 'Bank Employee' and 'Customer' roles
    to the particular bean methods that the role should be given access to.
    1. How does weblogic provide the facility to map the EJB deployment
    descriptor
    <security-role> to a particular weblogic principal (user orgroup)
    Or, should I say, how do I map the user or group to a
    deployment-descriptor defined role?In the deployment tool, once in the jar select the 'Security' item,create
    an application role (in your case it is probably best to create 2 security
    roles - the bank employee role refering to the bank employee group (usethe
    'in role' checkboxes, and the customer role refering to the customergroup -
    there may at some point be use for an allUsers role, which includes both
    groups, maybe not. What I am saying is that a role is made of a one ormore
    of Principals - in our case groups)
    In the Account Bean select the method permissions item, and create amethod
    permission perm-0, select the perm-0 item that has just popped up in the
    left hand window, tick the box for placeOnHold(), and the boxes for<remote>
    and <home> one level deeper than this in the tree (as an aside, I have
    absolutely no idea why there would be a 'home' box here, ho hum). Selectthe
    'bank employee' 'can invoke' tickbox
    Create perm-1, and do what you did above for 'withdraw()' and 'deposit()'
    methods, and the 'customer' tickbox
    I believe the documents say you would have to set up another permission to
    allow both groups access to the getBalance method, but in practive Ihaven't
    found this the case.
    The documentation for this is at
    http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_deploy.html#1102211
    (or
    search for 'Deploying EJBs with DeployerTool'
    2. Are there any administrative tools provided by weblogic to do
    this
    mapping ?The deployer tool. Otherwise I think it's the acse of writing your own xml
    files
    3. How much effort & complexity is involved in creating a custom
    realm
    Hmmm, depends - you could have the RDBMSRealm that is provided in'examples'
    in half an hour or so (there is a problem with one of the RDBMSUser's
    methods - getUserType or something like that - the solution can be foundin
    the newsgroups if you search), the same is probably true of the LDAPRealm,
    NTRealm etc (although I have never used these).
    Which one you choose depends on what equipment you have available,although
    I would say that the RDBMSRealm canuse a lot of optimisation
    Thanks,Welcome
    Raju
    "Terry" <[email protected]> wrote in message
    news:[email protected]...
    The Principals (i.e. groups and users) from your custom realm are used
    to
    define application roles for the EJBs, but, as far as I am aware youcannot
    use a custom implementation for the ACLs for EJBs
    terry
    r <[email protected]> wrote in message
    news:[email protected]...
    How does (or not) weblogic security tie into the EJB notion of rolebased
    control ? Can we create a 'custom' security mechanism for EJB (which
    basically uses the EJB facilities but extends it within the
    application)
    by
    using custom weblogic realms ?
    Thanks
    Raju

  • Weblogic.security.ldaprealmv2.LDAPRealmException

    Environment:
    WebLogic version: WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
    jdk: 1.3.1
    OS: Solaris 7
    LDAP server: iPlanet Directory Server 5.0
    Realm: LDAP2Realm CustomRealm weblogic.security.ldaprealmv2.LDAPRealm
    ISSUE:
    Certain LDAP users cause an Exception to propagate up to produce a 500
    internal server error. How can one programmetically catch this
    internal Exception? Why is this Exception thrown? I would have assumed
    that the WebLogic realm componet would would prevent such Exceptions
    from reaching the top?
    NOTE1: Other users that exhast their login tries DO NOT produces this
    Exception.
    NOTE2: I know this could very well be a bug in the iPlanet Directory
    Server 5.0 and/or the weblogic custom ream classes.
    EXCEPTION:
    <Apr 30, 2002 10:32:20 AM PDT> <Error> <HTTP>
    <[WebAppServletContext(8204614,dailyrpts,/dailyrpts)] Servlet failed
    with Exception
    netscape.ldap.LDAPException: error result (19); Exceed password retry
    limit. Please try later.; Constraint violation
    at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4852)
    at netscape.ldap.LDAPConnection.internalBind(LDAPConnection.java:1757)
    at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1294)
    at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1303)
    at netscape.ldap.LDAPConnection.bind(LDAPConnection.java:1613)
    at weblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:782)
    at weblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
    at weblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRealm.java:186)
    at weblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRealm.java:127)
    at weblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.java:110)
    at weblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
    at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
    at weblogic.security.acl.Realm.authenticate(Realm.java:200)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.servlet.security.internal.SecurityModule.checkAuthenticate(SecurityModule.java:262)
    at weblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecurityModule.java:217)
    at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:155)
    at weblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityModule.java:169)
    at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:144)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2467)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.security.ldaprealmv2.LDAPRealmException: caught unexpected
    exception - with nested exception:
    [netscape.ldap.LDAPException: error result (19); Exceed password retry
    limit. Please try later.; Constraint violation]
    at weblogic.security.ldaprealmv2.LDAPDelegate.handleException(LDAPDelegate.java:884)
    at weblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:801)
    at weblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
    at weblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRealm.java:186)
    at weblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRealm.java:127)
    at weblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.java:110)
    at weblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
    at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
    at weblogic.security.acl.Realm.authenticate(Realm.java:200)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.servlet.security.internal.SecurityModule.checkAuthenticate(SecurityModule.java:262)
    at weblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecurityModule.java:217)
    at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:155)
    at weblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityModule.java:169)
    at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:144)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2467)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Ok, so the only way to catch this is to create an "error-page" in the
    web.xml file that will catch this exception-type. I hoping I could do
    this in code somewhere...
    Thanks!
    Now I need to figure out why this Exceptionis being thrown!!
    My Research:
    http://developer.netscape.com/docs/manuals/dirsdk/jsdk30/exceptns.htm
    http://developer.netscape.com/docs/manuals/dirsdk/jsdk30/exceptn1.htm
    http://docs.iplanet.com/docs/manuals/dirsdk/jsdk41/Reference/netscape/ldap/LDAPException.html
    CONSTRAINT_VIOLATION
    An internal error occurred in the LDAP server.
    Constant of Class
    LDAPException
    Syntax
    public static final int CONSTRAINT_VIOLATION
    Description
    This exception corresponds to a result code of 19.
    "kirann" <[email protected]> wrote in message news:<[email protected]>...
    hi,
    you can catch this by defining.. <exception> in the web.xml.. see that
    dtd..
    thanks
    kiran
    "Matrix" <[email protected]> wrote in message
    news:[email protected]...
    Environment:
    WebLogic version: WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
    jdk: 1.3.1
    OS: Solaris 7
    LDAP server: iPlanet Directory Server 5.0
    Realm: LDAP2Realm CustomRealm weblogic.security.ldaprealmv2.LDAPRealm
    ISSUE:
    Certain LDAP users cause an Exception to propagate up to produce a 500
    internal server error. How can one programmetically catch this
    internal Exception? Why is this Exception thrown? I would have assumed
    that the WebLogic realm componet would would prevent such Exceptions
    from reaching the top?
    NOTE1: Other users that exhast their login tries DO NOT produces this
    Exception.
    NOTE2: I know this could very well be a bug in the iPlanet Directory
    Server 5.0 and/or the weblogic custom ream classes.
    EXCEPTION:
    <Apr 30, 2002 10:32:20 AM PDT> <Error> <HTTP>
    <[WebAppServletContext(8204614,dailyrpts,/dailyrpts)] Servlet failed
    with Exception
    netscape.ldap.LDAPException: error result (19); Exceed password retry
    limit. Please try later.; Constraint violation
    at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4852)
    atnetscape.ldap.LDAPConnection.internalBind(LDAPConnection.java:1757)
    atnetscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1294)
    atnetscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1303)
    at netscape.ldap.LDAPConnection.bind(LDAPConnection.java:1613)
    atweblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:78
    2)
    atweblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
    atweblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRea
    lm.java:186)
    atweblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRea
    lm.java:127)
    atweblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.ja
    va:110)
    atweblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
    atweblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
    at weblogic.security.acl.Realm.authenticate(Realm.java:200)
    atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    atweblogic.security.acl.internal.Security.authenticate(Security.java:125)
    atweblogic.servlet.security.internal.SecurityModule.checkAuthenticate(Security
    Module.java:262)
    atweblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecu
    rityModule.java:217)
    atweblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.
    java:155)
    atweblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityMod
    ule.java:169)
    atweblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
    tSecurityManager.java:144)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2467)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.security.ldaprealmv2.LDAPRealmException: caught unexpected
    exception - with nested exception:
    [netscape.ldap.LDAPException: error result (19); Exceed password retry
    limit. Please try later.; Constraint violation]
    atweblogic.security.ldaprealmv2.LDAPDelegate.handleException(LDAPDelegate.java
    :884)
    atweblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:80
    1)
    atweblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
    atweblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRea
    lm.java:186)
    atweblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRea
    lm.java:127)
    atweblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.ja
    va:110)
    atweblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
    atweblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
    at weblogic.security.acl.Realm.authenticate(Realm.java:200)
    atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    atweblogic.security.acl.internal.Security.authenticate(Security.java:125)
    atweblogic.servlet.security.internal.SecurityModule.checkAuthenticate(Security
    Module.java:262)
    atweblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecu
    rityModule.java:217)
    atweblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.
    java:155)
    atweblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityMod
    ule.java:169)
    atweblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
    tSecurityManager.java:144)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2467)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Weblogic.security.Encrypt  -and-  Not enough space

    This post has two questions.
    I have a simple application on wls9.2 that is a web front end to the weblogic.security.Encrypt command line utility. It seems to work fine, but after a little bit of use I am seeing the following:
    java.io.IOException: Not enough space
    at java.lang.UNIXProcess.forkAndExec(Native Method)
    at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
    at java.lang.ProcessImpl.start(ProcessImpl.java:65)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
    at java.lang.Runtime.exec(Runtime.java:591)
    at java.lang.Runtime.exec(Runtime.java:429)
    at java.lang.Runtime.exec(Runtime.java:326)
    at encrypt.wls92Encrypt(Unknown Source)
    at encrypt.doGet(Unknown Source)
    at encrypt.doPost(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    1) Here is the forking code:
    try {
    proc = Runtime.getRuntime().exec("java -Dweblogic.RootDirectory="+rootDir+" weblogic.security.Encrypt "+password);
    BufferedReader bf=new BufferedReader(new InputStreamReader(proc.getInputStream()));
    line=bf.readLine();
    bf.close();
    } catch (IOException e) {
    Is there a better way to do this, without forking? Seems odd to execute a java call, in java, just to get the encrypted string. I'd like to call weblogic.security.Encrypt inline, but have been unable to do so.
    2) Why would the Not enough space error creep up? Researching it, it seems like it is a swap problem, but that does not seem to be the case on our system. A top shows:
    Memory: 8192M phys mem, 2769M free mem, 5004M swap, 5004M free swap
    at the time of failure. Disk usage is looking great as well. The JVM heapsize is around 80% free. An lsof on the system shows about 150 open files on the managed server.
    Any ideas on how to troubleshoot this would be appreciated.
    Thanks

    I use CCleaner from the AppStore to delete the 'useless' stuff. It's free and works great for me

  • How to tell weblogic server which configuration I want to use

    Hi Everyone,
    I write the logmodule class, configuration class, Action class, client class
    and my policy file my.policy.
    I add the VM parameter when I start weblogic server
    "-Djava.security.auth.policy=D:\bea\wlserver6.1/lib/my.policy"
    But I don't know how to let weblogic server know my configuration class, so
    that the server will create it when my client code create LoginContext
    object.
    Some artical told me that add the configuration class name in java.security
    file, like the following
    login.configuration.provider=mypackage.myConfig
    unfortunately, it don't work :(
    I always got the exception message
    No Configuration Class Name Supplied
    Does anyone kindly tell me how to let the system know my configuration class
    name?
    Regards,
    xlzhou

    Hi,
    we are facing the same problem, if you get the solution would you please help
    us out?
    Regards
    Sudipto
    [email protected] (Joe Zhou) wrote:
    I almost got same problem.
    I wrote a deme which is using jaas.
    The client part:
    Properties property = new Properties(System.getProperties());
    property.put("weblogic.security.jaas.ServerURL",
    "http://localhost:7001");
    System.setProperties(property);
    // Set configuration class name to load SampleConfiguration, the
    //Configuration for the JAAS code example
    property = new Properties(System.getProperties());
    property.put("weblogic.security.jaas.Configuration",
    "test.servlets.TestConfig");
    System.setProperties(property);
    // Set Configuration file name to load sample configuration policy
    file.
    property = new Properties(System.getProperties());
    property.put("weblogic.security.jaas.Policy",
    "C:/bea/wlserver6.1/config/mydomain/Test.policy");
    System.setProperties(property);
    loginContext = new LoginContext("TestPolicy", new
    MyCallbackHandler());
    The Test.policy:
    TestPolicy
    test.servlets.TestLoginModule required debug=true;
    And I add "-Djava.security.auth.policy=%WL_HOME%\config\mydomain\Test.policy"
    when I start weblogic server.
    But when I run the code, I got the exception:
    Invalid Configuration Class Name: test.servlets.TestConfig
    java.lang.NullPointerException
    at javax.security.auth.login.LoginContext.loadLoginModule(LoginContext.j
    ava:101)
    at javax.security.auth.login.LoginContext.<init>(LoginContext.java:54)
    at test.servlets.TestSecure.doPost(TestSecure.java:69)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:2456)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2039)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Seems the problem is in my TestConfig.
    I just copy the SampleConfig.java as my TestConfig.java (modified a
    little) and copy the ConfigParser.java (those are in the
    samples\examples\security\jaas\examples\security\jaas)
    Any suggestion???
    BTW, all the necessary classes is in the .war file.
    Thanks in advance.
    Joe
    "Xiao Ling Zhou" <[email protected]> wrote in message news:<[email protected]>...
    Hi Everyone,
    I write the logmodule class, configuration class, Action class, clientclass
    and my policy file my.policy.
    I add the VM parameter when I start weblogic server
    "-Djava.security.auth.policy=D:\bea\wlserver6.1/lib/my.policy"
    But I don't know how to let weblogic server know my configuration class,so
    that the server will create it when my client code create LoginContext
    object.
    Some artical told me that add the configuration class name in java.security
    file, like the following
    login.configuration.provider=mypackage.myConfig
    unfortunately, it don't work :(
    I always got the exception message
    No Configuration Class Name Supplied
    Does anyone kindly tell me how to let the system know my configurationclass
    name?
    Regards,
    xlzhou

  • Adminserver throws weblogic.security.service.SecurityServiceException

    Hi all,
    When i installed weblogic 10.3.3 with java1.6 on RHEL 5.5 & created the domain. After the creation , i am not able to star the Admin server,it is throwing the below error. Do anyone have idea ,how to resolve this issue ?
    ####<Oct 28, 2010 3:38:41 AM PDT> <Error> <Security> <Unknown> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288262321492> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.
    weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError
    at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
    at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
    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)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.ExceptionInInitializerError
    at com.octetstring.vde.util.guid.GuidGenerator.nextGuidInBytes(GuidGenerator.java:125)
    at com.octetstring.vde.util.guid.Guid.<init>(Guid.java:84)
    at com.octetstring.vde.backend.standard.BackendStandard.add(BackendStandard.java:379)
    at com.octetstring.vde.backend.BackendHandler.add(BackendHandler.java:460)
    at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:279)
    at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:235)
    at weblogic.security.utils.ProviderUtils.loadFullLDIFTemplate(ProviderUtils.java:739)
    at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:583)
    at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:489)
    at weblogic.security.utils.ProviderUtils.loadLDIFAuthenticatorTemplate(ProviderUtils.java:316)
    at weblogic.security.providers.authentication.DefaultAuthenticationProviderImpl.initialize(DefaultAuthenticationProviderImpl.java:128)
    at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:65)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
    at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)
    at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)
    at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
    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)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.NullPointerException
    at java.lang.System.arraycopy(Native Method)
    at com.octetstring.vde.util.guid.GuidParamGenerator.generateNodeID(GuidParamGenerator.java:47)
    at com.octetstring.vde.util.guid.GuidStateManager.initializeGUIDParameters(GuidStateManager.java:59)
    at com.octetstring.vde.util.guid.GuidStateManager.<init>(GuidStateManager.java:30)
    at com.octetstring.vde.util.guid.GuidStateManager.<clinit>(GuidStateManager.java:23)
    at com.octetstring.vde.util.guid.GuidGenerator.nextGuidInBytes(GuidGenerator.java:125)
    at com.octetstring.vde.util.guid.Guid.<init>(Guid.java:84)
    at com.octetstring.vde.backend.standard.BackendStandard.add(BackendStandard.java:379)
    at com.octetstring.vde.backend.BackendHandler.add(BackendHandler.java:460)
    at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:279)
    at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:235)
    at weblogic.security.utils.ProviderUtils.loadFullLDIFTemplate(ProviderUtils.java:739)
    at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:583)
    at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:489)
    at weblogic.security.utils.ProviderUtils.loadLDIFAuthenticatorTemplate(ProviderUtils.java:316)
    at weblogic.security.providers.authentication.DefaultAuthenticationProviderImpl.initialize(DefaultAuthenticationProviderImpl.java:128)
    at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:65)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
    at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)
    at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)
    at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
    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)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    thanks
    Arun

    Hi,
    It looks like your security services initilization has some problem.Please try to do below step.
    Please login to the Database and then run the below SQL file to execute different queries mentioned in this file:
    Suppose Database User Login is “weblogic” then login to Database with this credential and run the script under $BEA_HOME\wlserver_10.3\server\lib\rdbms_security_store_oracle.sql
    Then restart your Server.

Maybe you are looking for