WebLogic Security in sp8

"There is a security issue with the JDK that we are using, 1.2.2_05a. It can only be exploited in certain circumstances. I have some questions that I can not find an answer to on ASK BEA:1. Is WebLogic 5.1 sp8 vulnerable to the exploit described in Sun Security Bulletin

为了方便Weblogic用户管理JKS证书，我发布了一个Eclipse插件，代号SecureX，该插件将集成Keytool, Axis数字签名，加密，和SSO/SSL向导，目前版本为1.0.0，改自于KeytoolGUI1.6版本。
作了不少的增强，原来的版本已经停止开发并被作者商业化，开源版本以后将由我提供：）
SecureX 的URL: http://www.blogjava.net/openssl/archive/2006/03/17/35781.html
关于SecureX，请参看http://www.blogjava.net/openssl/archive/2006/02/08/29886.aspx
该Project遵循GPL，参见https://sourceforge.net/projects/securex/
源代码将在2.0发布到SF。
代替Keytool的图形化界面，增加了数字签名功能，原来的版本来自于Keytool Gui 1.6（基于SWing）,我重写了SWT界面，集成到SecureX并以SecureX为基础，不断扩展Java Security功能，包括加密，签名，SSO向导，SSL向导之类的功能。
下载：
http://www.blogjava.net/Files/openssl/plugins.part1.rar
http://www.blogjava.net/Files/openssl/plugins.part2.rar
http://www.blogjava.net/Files/openssl/plugins.part3.rar
http://www.blogjava.net/Files/openssl/plugins.part4.rar
http://www.blogjava.net/Files/openssl/plugins.part5.rar
http://www.blogjava.net/Files/openssl/plugins.part6.rar
http://www.blogjava.net/Files/openssl/plugins.part7.rar
下载完毕后，解压到plugins目录，然后找到
其子目录SecureX_1.0.0
然后，将其整个Copy到Eclipse目录下的Plugin目录下，重启Eclipse，
然后点击菜单项Securex下KeyTool，就可以运行。
如对SecureX有兴趣，请加入SecuritySite群（14966586）或者email给我：openssl(at)163.com

Similar Messages

Weblogic 5.1 SP8 on WIN NT Hangs

Hi,
I have the following configuration being tested for load.
Weblogic 5.1 SP8, Windows NT, Java 1.2.2, Oracle 8.1.6.
I am running load scripts that access JSP. There are about 15 users doing
fixed number of different things repeatedly i.e. they login, do a few things
and logout. Everything runs fine for about 1 to 2 hours and after that I
observe CPU at 100 % and users cannot do anything. I took the thread dump,
but this does not reveal any user doing any CPU intesive operations. All the
JSP being accessed do finite number of things that take finite time. I do
not see anything that should make the CPU shoot up to 100 %. Do you have any
suggestions on how to debug this problem ? I am enclosing the thread dump
(do you think it is odd that all threads are waiting on signal dispatcher).
Would really appreciate some suggestions.
Thanks,
Mihir
Full thread dump Classic VM (JDK-1.2.2-W, native threads):
"HighPriority TimeEventGenerator" (TID:0x6bd85f8,
sys_thread_t:0x24c7fdc8, state:CW, native ID:0x648) prio=9
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java, Compiled
Code)
at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"ListenThread" (TID:0x632eb98, sys_thread_t:0x24ed8f80, state:R, native
ID:0x94) prio=5
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java, Compiled Code)
at java.net.ServerSocket.implAccept(ServerSocket.java, Compiled Code)
at java.net.ServerSocket.accept(ServerSocket.java, Compiled Code)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java, Compiled Code)
"NBExecuteThread-1" (TID:0x6323590, sys_thread_t:0x2245f660, state:CW,
native ID:0x4b4) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"NBExecuteThread-0" (TID:0x6323300, sys_thread_t:0x2245e530, state:CW,
native ID:0x618) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-14" (TID:0x6323218, sys_thread_t:0x22448ff0, state:R,
native ID:0x260) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-13" (TID:0x63230e0, sys_thread_t:0x22448e80, state:MW,
native ID:0x534) prio=5
at java.lang.reflect.Method.invoke(Native Method)
at com.mycompany.expr.fn.Invoke.eval(Invoke.java, Compiled Code)
at
com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
Compiled Code)
at jsp._myapp._login._jspService(_login.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-12" (TID:0x6322fb0, sys_thread_t:0x22448d10, state:R,
native ID:0x540) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-11" (TID:0x6322e78, sys_thread_t:0x22448ba0, state:R,
native ID:0x5cc) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-10" (TID:0x6322a98, sys_thread_t:0x22448a30, state:R,
native ID:0x3ec) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-9" (TID:0x6322968, sys_thread_t:0x2244a0a0, state:R,
native ID:0x47c) prio=5
"ExecuteThread-8" (TID:0x6322838, sys_thread_t:0x22449f30, state:MW,
native ID:0x550) prio=5
at java.lang.reflect.Method.invoke(Native Method)
at
com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
Compiled Code)
at jsp._myapp._login._jspService(_login.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-7" (TID:0x6322708, sys_thread_t:0x22449dc0, state:MW,
native ID:0x6c0) prio=5
"ExecuteThread-6" (TID:0x63225d0, sys_thread_t:0x22449c50, state:MW,
native ID:0x624) prio=5
"ExecuteThread-5" (TID:0x6322520, sys_thread_t:0x22449ae0, state:MW,
native ID:0x6dc) prio=5
"ExecuteThread-4" (TID:0x6322370, sys_thread_t:0x2244ed68, state:MW,
native ID:0x60c) prio=5
at java.lang.reflect.Method.invoke(Native Method)
at
com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
Compiled Code)
at jsp._myapp._login._jspService(_login.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-3" (TID:0x6322240, sys_thread_t:0x2244ebf8, state:R,
native ID:0x62c) prio=5
"ExecuteThread-2" (TID:0x6321fb8, sys_thread_t:0x2244ea88, state:R,
native ID:0x6c4) prio=5
"ExecuteThread-1" (TID:0x6321d30, sys_thread_t:0x22447930, state:MW,
native ID:0x53c) prio=5
"ExecuteThread-0" (TID:0x63217c0, sys_thread_t:0x2242fac8, state:MW,
native ID:0x6a0) prio=5
"TimeEventGenerator" (TID:0x63141c8, sys_thread_t:0x2242bb48, state:CW,
native ID:0x5c0) prio=5
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java, Compiled
Code)
at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" (TID:0x6313b30, sys_thread_t:0x223c0de8, state:CW,
native ID:0x6ac) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at
weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java,
Compiled Code)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java,
Compiled Code)
"SymcJIT-LazyCompilation-1" (TID:0x61afc60, sys_thread_t:0x219a5d48,
state:CW, native ID:0x6bc) prio=1
at SymantecJITCompilationThread.DoCompileMethod(Native Method)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
Code)
"SymcJIT-LazyCompilation-0" (TID:0x61afca8, sys_thread_t:0x219a4c18,
state:CW, native ID:0x640) prio=1
at SymantecJITCompilationThread.DoCompileMethod(Native Method)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
Code)
"SymcJIT-LazyCompilation-PA" (TID:0x61afc70, sys_thread_t:0x219a3ae8,
state:CW, native ID:0x6a8) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
Code)
"Finalizer" (TID:0x61a9320, sys_thread_t:0x2105dfe0, state:CW, native
ID:0x3cc) prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
"Reference Handler" (TID:0x61a93b0, sys_thread_t:0x2105c638, state:CW,
native ID:0x6b8) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
"Signal dispatcher" (TID:0x61a93e0, sys_thread_t:0x21059408, state:R,
native ID:0x498) prio=5
"main" (TID:0x61a91e0, sys_thread_t:0x2f5f90, state:CW, native ID:0x710)
prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:107)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
Monitor Cache Dump:
weblogic.time.common.internal.TimeTable@6BD8660/6F2AFE8: <unowned>
Waiting to be notified:
"HighPriority TimeEventGenerator" (0x24c7fdc8)
java.net.PlainSocketImpl@6BDBA70/7357B08: owner "ListenThread"
(0x24ed8f80) 1 entry
oracle.jdbc.driver.OraclePreparedStatement@5E403B8/D4CF580: owner
"ExecuteThread-8" (0x22449f30) 1 entry
weblogic.kernel.ExecuteThread@6323590/7A400B0: <unowned>
Waiting to be notified:
"NBExecuteThread-1" (0x2245f660)
weblogic.t3.srvr.T3Srvr@61CE7B0/6FC2158: <unowned>
Waiting to be notified:
"main" (0x2f5f90)
SymantecJITCompilationThread@61AFCA8/6EB0288: <unowned>
Waiting to be notified:
"SymcJIT-LazyCompilation-PA" (0x219a3ae8)
com.mycompany.server.proxy.MycompanyProxyBeanEOImpl@5F6FCE0/CBCB850:
owner "ExecuteThread-8" (0x22449f30) 1 entry
weblogic.security.SpinnerThread@6313B30/79AEB20: <unowned>
Waiting to be notified:
"SpinnerRandomSource" (0x223c0de8)
java.lang.ref.ReferenceQueue$Lock@61A9338/6E786E8: <unowned>
Waiting to be notified:
"Finalizer" (0x2105dfe0)
oracle.jdbc.ttc7.TTC7Protocol@63653F0/6FFF008: owner "ExecuteThread-1"
(0x22447930) 1 entry
java.lang.Object@62FCAA8/6FB1388: owner "ExecuteThread-4" (0x2244ed68) 1
entry
java.lang.ref.Reference$Lock@61A93C0/6E78228: <unowned>
Waiting to be notified:
"Reference Handler" (0x2105c638)
weblogic.kernel.ExecuteThread@6323300/7A3F210: <unowned>
Waiting to be notified:
"NBExecuteThread-0" (0x2245e530)
weblogic.time.common.internal.TimeTable@6314D88/79BB7C8: <unowned>
Waiting to be notified:
"TimeEventGenerator" (0x2242bb48)
weblogic.jdbc.common.internal.ConnectionEnv@63652E8/6FFDF70: owner
"ExecuteThread-1" (0x22447930) 1 entry
oracle.jdbc.driver.OracleStatement@5E3EF90/D4DD8C0: owner
"ExecuteThread-1" (0x22447930) 1 entry
Registered Monitor Dump:
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Lazy Queue Lock: <unowned>
Waiting to be notified:
"SymcJIT-LazyCompilation-0" (0x219a4c18)
"SymcJIT-LazyCompilation-1" (0x219a5d48)
SymcJIT Method Monitor: <unowned>
SymcJIT Method List Monitor: <unowned>
SymcJIT Lock: <unowned>
utf8 hash
table: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class linking lock: <unowned>
System class loader lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Monitor cache lock: owner "Signal dispatcher" (0x21059408) 1 entry
Waiting to enter:
"ExecuteThread-13" (0x22448e80)
"ExecuteThread-8" (0x22449f30)
"ExecuteThread-7" (0x22449dc0)
"ExecuteThread-6" (0x22449c50)
"ExecuteThread-5" (0x22449ae0)
"ExecuteThread-4" (0x2244ed68)
"ExecuteThread-1" (0x22447930)
"ExecuteThread-0" (0x2242fac8)
Thread queue lock: owner "Signal dispatcher" (0x21059408) 1 entry
Monitor registry: owner "Signal dispatcher" (0x21059408) 1 entry

Going through the thread dump
1. it looks like you are not using the Performance Packs (check if
weblogic.system.nativeIO.enable = true in weblogic.properties)
2. since it happens only after about an hour the garbage collector might be
busy which consumes the processor, try using incremental GC while you start
the weblogic server. This could be done with -Xincgc flag.
Hope and wish this solves your problem.
- Nirmal R.
"Michael Reiche" <[email protected]> wrote in message
news:[email protected]...
It looks like the Symantec JIT Compiler is busy compiling methods andthat
the ExecuteThreads (your JSPs) are waiting for them to finish so they can
execute a method (presumably the method that the JIT is busy compiling) -
just a guess.
You may want to try a different JVM - maybe 1.3.0
You could try turning off JIT - then your app would run impossibly slow,but
it would still run.
If you have any large methods - you could try and make them smaller - JVMs
have a hard time with large/complex methods - especially nested try/catch
blocks.
There's no need to cross post - a lot of people read all the groups.
Mike
"Mihir Mehta" <[email protected]> wrote in message
news:[email protected]...
Hi,
I have the following configuration being tested for load.
Weblogic 5.1 SP8, Windows NT, Java 1.2.2, Oracle 8.1.6.
I am running load scripts that access JSP. There are about 15 users
doing
fixed number of different things repeatedly i.e. they login, do a fewthings
and logout. Everything runs fine for about 1 to 2 hours and after that
I
observe CPU at 100 % and users cannot do anything. I took the threaddump,
but this does not reveal any user doing any CPU intesive operations. Allthe
JSP being accessed do finite number of things that take finite time. I
do
not see anything that should make the CPU shoot up to 100 %. Do you haveany
suggestions on how to debug this problem ? I am enclosing the thread
dump
(do you think it is odd that all threads are waiting on signaldispatcher).
Would really appreciate some suggestions.
Thanks,
Mihir
Full thread dump Classic VM (JDK-1.2.2-W, native threads):
"HighPriority TimeEventGenerator" (TID:0x6bd85f8,
sys_thread_t:0x24c7fdc8, state:CW, native ID:0x648) prio=9
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java,Compiled
Code)
at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.ja
va
, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"ListenThread" (TID:0x632eb98, sys_thread_t:0x24ed8f80, state:R,native
ID:0x94) prio=5
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java, Compiled Code)
at java.net.ServerSocket.implAccept(ServerSocket.java, Compiled Code)
at java.net.ServerSocket.accept(ServerSocket.java, Compiled Code)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java, Compiled Code)
"NBExecuteThread-1" (TID:0x6323590, sys_thread_t:0x2245f660,
state:CW,
native ID:0x4b4) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"NBExecuteThread-0" (TID:0x6323300, sys_thread_t:0x2245e530,state:CW,
native ID:0x618) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-14" (TID:0x6323218, sys_thread_t:0x22448ff0, state:R,
native ID:0x260) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-13" (TID:0x63230e0, sys_thread_t:0x22448e80,
state:MW,
native ID:0x534) prio=5
at java.lang.reflect.Method.invoke(Native Method)
at com.mycompany.expr.fn.Invoke.eval(Invoke.java, Compiled Code)
at
com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
Compiled Code)
at jsp._myapp._login._jspService(_login.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-12" (TID:0x6322fb0, sys_thread_t:0x22448d10, state:R,
native ID:0x540) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-11" (TID:0x6322e78, sys_thread_t:0x22448ba0, state:R,
native ID:0x5cc) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-10" (TID:0x6322a98, sys_thread_t:0x22448a30, state:R,
native ID:0x3ec) prio=5
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-9" (TID:0x6322968, sys_thread_t:0x2244a0a0, state:R,
native ID:0x47c) prio=5
"ExecuteThread-8" (TID:0x6322838, sys_thread_t:0x22449f30, state:MW,
native ID:0x550) prio=5
at java.lang.reflect.Method.invoke(Native Method)
at
com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
Compiled Code)
at jsp._myapp._login._jspService(_login.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-7" (TID:0x6322708, sys_thread_t:0x22449dc0, state:MW,
native ID:0x6c0) prio=5
"ExecuteThread-6" (TID:0x63225d0, sys_thread_t:0x22449c50, state:MW,
native ID:0x624) prio=5
"ExecuteThread-5" (TID:0x6322520, sys_thread_t:0x22449ae0, state:MW,
native ID:0x6dc) prio=5
"ExecuteThread-4" (TID:0x6322370, sys_thread_t:0x2244ed68, state:MW,
native ID:0x60c) prio=5
at java.lang.reflect.Method.invoke(Native Method)
at
com.mycompany.jsp.SessionPageBean.performAllActions(SessionPageBean.java,
Compiled Code)
at jsp._myapp._login._jspService(_login.java, Compiled Code)
at weblogic.servlet.jsp.JspBase.service(JspBase.java, Compiled Code)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
>
, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java, Compiled Code)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java, Compiled Code)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
"ExecuteThread-3" (TID:0x6322240, sys_thread_t:0x2244ebf8, state:R,
native ID:0x62c) prio=5
"ExecuteThread-2" (TID:0x6321fb8, sys_thread_t:0x2244ea88, state:R,
native ID:0x6c4) prio=5
"ExecuteThread-1" (TID:0x6321d30, sys_thread_t:0x22447930, state:MW,
native ID:0x53c) prio=5
"ExecuteThread-0" (TID:0x63217c0, sys_thread_t:0x2242fac8, state:MW,
native ID:0x6a0) prio=5
"TimeEventGenerator" (TID:0x63141c8, sys_thread_t:0x2242bb48,state:CW,
native ID:0x5c0) prio=5
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java,Compiled
Code)
at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" (TID:0x6313b30, sys_thread_t:0x223c0de8,state:CW,
native ID:0x6ac) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at
weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java,
Compiled Code)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java,
Compiled Code)
"SymcJIT-LazyCompilation-1" (TID:0x61afc60, sys_thread_t:0x219a5d48,
state:CW, native ID:0x6bc) prio=1
at SymantecJITCompilationThread.DoCompileMethod(Native Method)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
Code)
"SymcJIT-LazyCompilation-0" (TID:0x61afca8, sys_thread_t:0x219a4c18,
state:CW, native ID:0x640) prio=1
at SymantecJITCompilationThread.DoCompileMethod(Native Method)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
Code)
"SymcJIT-LazyCompilation-PA" (TID:0x61afc70,sys_thread_t:0x219a3ae8,
state:CW, native ID:0x6a8) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled
Code)
"Finalizer" (TID:0x61a9320, sys_thread_t:0x2105dfe0, state:CW,native
ID:0x3cc) prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, CompiledCode)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, CompiledCode)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
"Reference Handler" (TID:0x61a93b0, sys_thread_t:0x2105c638,
state:CW,
native ID:0x6b8) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
"Signal dispatcher" (TID:0x61a93e0, sys_thread_t:0x21059408,state:R,
native ID:0x498) prio=5
"main" (TID:0x61a91e0, sys_thread_t:0x2f5f90, state:CW, nativeID:0x710)
prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:107)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
Monitor Cache Dump:
weblogic.time.common.internal.TimeTable@6BD8660/6F2AFE8: <unowned>
Waiting to be notified:
"HighPriority TimeEventGenerator" (0x24c7fdc8)
java.net.PlainSocketImpl@6BDBA70/7357B08: owner "ListenThread"
(0x24ed8f80) 1 entry
oracle.jdbc.driver.OraclePreparedStatement@5E403B8/D4CF580: owner
"ExecuteThread-8" (0x22449f30) 1 entry
weblogic.kernel.ExecuteThread@6323590/7A400B0: <unowned>
Waiting to be notified:
"NBExecuteThread-1" (0x2245f660)
weblogic.t3.srvr.T3Srvr@61CE7B0/6FC2158: <unowned>
Waiting to be notified:
"main" (0x2f5f90)
SymantecJITCompilationThread@61AFCA8/6EB0288: <unowned>
Waiting to be notified:
"SymcJIT-LazyCompilation-PA" (0x219a3ae8)
com.mycompany.server.proxy.MycompanyProxyBeanEOImpl@5F6FCE0/CBCB850:
owner "ExecuteThread-8" (0x22449f30) 1 entry
weblogic.security.SpinnerThread@6313B30/79AEB20: <unowned>
Waiting to be notified:
"SpinnerRandomSource" (0x223c0de8)
java.lang.ref.ReferenceQueue$Lock@61A9338/6E786E8: <unowned>
Waiting to be notified:
"Finalizer" (0x2105dfe0)
oracle.jdbc.ttc7.TTC7Protocol@63653F0/6FFF008: owner
"ExecuteThread-1"
(0x22447930) 1 entry
java.lang.Object@62FCAA8/6FB1388: owner "ExecuteThread-4"(0x2244ed68)
1
entry
java.lang.ref.Reference$Lock@61A93C0/6E78228: <unowned>
Waiting to be notified:
"Reference Handler" (0x2105c638)
weblogic.kernel.ExecuteThread@6323300/7A3F210: <unowned>
Waiting to be notified:
"NBExecuteThread-0" (0x2245e530)
weblogic.time.common.internal.TimeTable@6314D88/79BB7C8: <unowned>
Waiting to be notified:
"TimeEventGenerator" (0x2242bb48)
weblogic.jdbc.common.internal.ConnectionEnv@63652E8/6FFDF70: owner
"ExecuteThread-1" (0x22447930) 1 entry
oracle.jdbc.driver.OracleStatement@5E3EF90/D4DD8C0: owner
"ExecuteThread-1" (0x22447930) 1 entry
Registered Monitor Dump:
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Lazy Queue Lock: <unowned>
Waiting to be notified:
"SymcJIT-LazyCompilation-0" (0x219a4c18)
"SymcJIT-LazyCompilation-1" (0x219a5d48)
SymcJIT Method Monitor: <unowned>
SymcJIT Method List Monitor: <unowned>
SymcJIT Lock: <unowned>
utf8 hash
table: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class linking lock: <unowned>
System class loader lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Monitor cache lock: owner "Signal dispatcher" (0x21059408) 1 entry
Waiting to enter:
"ExecuteThread-13" (0x22448e80)
"ExecuteThread-8" (0x22449f30)
"ExecuteThread-7" (0x22449dc0)
"ExecuteThread-6" (0x22449c50)
"ExecuteThread-5" (0x22449ae0)
"ExecuteThread-4" (0x2244ed68)
"ExecuteThread-1" (0x22447930)
"ExecuteThread-0" (0x2242fac8)
Thread queue lock: owner "Signal dispatcher" (0x21059408) 1 entry
Monitor registry: owner "Signal dispatcher" (0x21059408) 1 entry

Error:- weblogic.security.SecurityInitializationException: Authentication

Hi,
I am getting below error when ever i am trying to start the Managed server in cluster environment(unix).
I am able to start the server on local machine but in case of remote machine its not gettig started.
I have tried most of the steps as mentioned below:-
1) Changed the weblogic passowrd.
2) Delete boot.properties.
3) deleted $DOMAIN_DIR\servers\<admin-server-name>\data\ldap
4) Followed below post also but nothing worked:-
https://forums.oracle.com/forums/thread.jspa?threadID=956750&start=30&tstart=0
####<Nov 14, 2011 7:41:28 PM IST> <Info> <WebLogicServer> <infva05177.vshodc.lntinfotech.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1321279888310> <BEA-000000> <WebLogic Server "soa_server2" version:
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
####<Nov 14, 2011 7:41:28 PM IST> <Notice> <Log Management> <infva05177.vshodc.lntinfotech.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1321279888419> <BEA-170019> <The server log file /home/oracle/Oracle/Middleware/user_projects/domains/domain_cluster/servers/soa_server2/logs/soa_server2.log is opened. All server side log events will be written to this file.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Log Management> <infva05177.vshodc.lntinfotech.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1321279888426> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Diagnostics> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888494> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888560> <BEA-002622> <The protocol "t3" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888560> <BEA-002622> <The protocol "t3s" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888560> <BEA-002622> <The protocol "http" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888560> <BEA-002622> <The protocol "https" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888561> <BEA-002622> <The protocol "iiop" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888562> <BEA-002622> <The protocol "iiops" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888562> <BEA-002622> <The protocol "ldap" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888562> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888564> <BEA-002622> <The protocol "cluster" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888565> <BEA-002622> <The protocol "clusters" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888568> <BEA-002622> <The protocol "snmp" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888568> <BEA-002622> <The protocol "admin" is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888569> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Nov 14, 2011 7:41:28 PM IST> <Info> <RJVM> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279888583> <BEA-000570> <Network Configuration for Channel "soa_server2"
Listen Address          172.17.103.42:8101
Public Address          N/A
Http Enabled          true
Tunneling Enabled     false
Outbound Enabled     false
Admin Traffic Enabled     true>
####<Nov 14, 2011 7:41:29 PM IST> <Info> <Server> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279889336> <BEA-002609> <Channel Service initialized.>
####<Nov 14, 2011 7:41:29 PM IST> <Info> <Socket> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279889410> <BEA-000436> <Allocating 4 reader threads.>
####<Nov 14, 2011 7:41:29 PM IST> <Info> <Socket> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279889412> <BEA-000446> <Native IO Enabled.>
####<Nov 14, 2011 7:41:29 PM IST> <Info> <IIOP> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279889612> <BEA-002014> <IIOP subsystem enabled.>
####<Nov 14, 2011 7:41:32 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279892649> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
####<Nov 14, 2011 7:41:33 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279893102> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
####<Nov 14, 2011 7:41:33 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279893224> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_qMT60FRl3kIPYftFoWhBFbhSxuY=>
####<Nov 14, 2011 7:41:33 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279893501> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find /home/oracle/Oracle/Middleware/user_projects/domains/domain_cluster/servers/soa_server2/data/ldap/XACMLAuthorizermyrealmInit.initialized, will load full LDIFT.>
####<Nov 14, 2011 7:41:33 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279893509> <BEA-090074> <Initializing Authorizer provider using LDIF template file /home/oracle/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift.>
####<Nov 14, 2011 7:41:33 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279893921> <BEA-090075> <The Authorizer provider has had its LDIF information loaded from: /home/oracle/Oracle/Middleware/wlserver_10.3/server/lib/XACMLAuthorizerInit.ldift>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894240> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find /home/oracle/Oracle/Middleware/user_projects/domains/domain_cluster/servers/soa_server2/data/ldap/DefaultCredentialMappermyrealmInit.initialized, will load full LDIFT.>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894240> <BEA-090827> <LDIF template file /home/oracle/Oracle/Middleware/wlserver_10.3/server/lib/DefaultCredentialMapperInit.ldift was empty. The WebLogic provider CredentialMapper has been bootstrapped but has not been initialized with any LDIF data.>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894250> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find /home/oracle/Oracle/Middleware/user_projects/domains/domain_cluster/servers/soa_server2/data/ldap/XACMLRoleMappermyrealmInit.initialized, will load full LDIFT.>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894251> <BEA-090074> <Initializing RoleMapper provider using LDIF template file /home/oracle/Oracle/Middleware/user_projects/domains/domain_cluster/security/XACMLRoleMapperInit.ldift.>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894265> <BEA-090075> <The RoleMapper provider has had its LDIF information loaded from: /home/oracle/Oracle/Middleware/user_projects/domains/domain_cluster/security/XACMLRoleMapperInit.ldift>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894442> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server soa_server2 for security realm myrealm.>
####<Nov 14, 2011 7:41:34 PM IST> <Notice> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894442> <BEA-090082> <Security initializing using security realm myrealm.>
####<Nov 14, 2011 7:41:34 PM IST> <Critical> <Security> <infva05177.vshodc.lntinfotech.com> <soa_server2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1321279894594> <BEA-090403> <Authentication for user weblogic denied>
####<Nov 14, 2011 7:41:34 PM IST> <Critical> <WebLogicServer> <infva05177.vshodc.lntinfotech.com> <soa_server2> <Main Thread> <<WLS Kernel>> <> <> <1321279894596> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
     at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy28.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy46.authenticate(Unknown Source)
     at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:348)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Nov 14, 2011 7:41:34 PM IST> <Notice> <WebLogicServer> <infva05177.vshodc.lntinfotech.com> <soa_server2> <Main Thread> <<WLS Kernel>> <> <> <1321279894605> <BEA-000365> <Server state changed to FAILED>
####<Nov 14, 2011 7:41:34 PM IST> <Error> <WebLogicServer> <infva05177.vshodc.lntinfotech.com> <soa_server2> <Main Thread> <<WLS Kernel>> <> <> <1321279894605> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Nov 14, 2011 7:41:34 PM IST> <Notice> <WebLogicServer> <infva05177.vshodc.lntinfotech.com> <soa_server2> <Main Thread> <<WLS Kernel>> <> <> <1321279894608> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Nov 14, 2011 7:41:34 PM IST> <Info> <WebLogicServer> <infva05177.vshodc.lntinfotech.com> <soa_server2> <Main Thread> <<WLS Kernel>> <> <> <1321279894618> <BEA-000236> <Stopping execute threads.>
Please help.
thanks in advance

I've tried every trick in the book but no luck and finally I found a solution for this problem. Maybe it is not the best practice but it works:
1-Uninstall JDeveloper.
2-Delete Oracle Middleware file located in C:\Oracle
3-Delete the JDeveloper file located in C:\Users\MyUser\AppData\Roaming (Because the integrated Weblogic server is actually there)
4-Reinstall JDeveloper
That solved the issue.
Thanks

Weblogic.security.internal.SerializedSystemIniException

While starting weblogic server, I am getting the following error,
Exception raised:
weblogic.security.internal.SerializedSystemIniException: Version mismatch. have
0, expected 1
     at weblogic.security.internal.SerializedSystemIni.<init>(SerializedSystemIni.java:119)
     at weblogic.security.internal.SerializedSystemIni.getEncryptionService(SerializedSystemIni.java:208)
     at weblogic.management.internal.EncryptedData.getEncryptionService(EncryptedData.java:82)
Can anybody give a clue in this to resolve urgently?

It seems like your SerializedSystemIni.dat is currupted.
Do you have SerializedSystemIni.dat and fileRealm.property from any other
working domain?
Please try to replace both of them and see if this fixes the problem.
-utpal
"Ramanan " <[email protected]> wrote in message
news:[email protected]..
>
While starting weblogic server, I am getting the following error,
Exception raised:
weblogic.security.internal.SerializedSystemIniException: Version mismatch.have
0, expected 1
atweblogic.security.internal.SerializedSystemIni.<init>(SerializedSystemIni.ja
va:119)
atweblogic.security.internal.SerializedSystemIni.getEncryptionService(Serializ
edSystemIni.java:208)
atweblogic.management.internal.EncryptedData.getEncryptionService(EncryptedDat
a.java:82)
>
Can anybody give a clue in this to resolve urgently?

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

The weblogic.security.Security.runAs() and JAAS Subject

Let say that I have Java client with some JAAS code that authenticates
the user. The LoginContext generates a Subject containing the Principal
name of the authenticated user, but also some private credentials that
makes the Subject secure.
Now I want to call an EJB on WLS.
Having JNDI (EJB) code inside a PriviledgesAction and using the
weblogic.security.Security.runAs() method, I assume that the Subject is
sent over the wire with the EJB call. If not, please correct me.
Question is: How does WLS authenticate this call? What modules are
called? IdentityAsserter? LoginModule? Is the Subject simply assumed
"valid"? Any documentation describing how this is done?
/Bo

Hi,
Problem is solved, we also got security exception when we tried to call MBeans.For this to work we have to set
-Dweblogic.disableMBeanAuthorization=true in weblogic startup script so that our application can access MBeans.
Thanks
girish

New to Weblogic Security

I have an ORACLE database which contains a table of 100s of users and passwords with their group information. I developed a Webapplication (in Tomcat) in which one of the servlets works as authenticator for the user logging in by fetching row from the datbase and validating him.(This is a simple authentication)
Now I have switched to Weblogic platform 8.1 SP2 and am completely new to Weblogic Security. I want to use Weblogic security features for my application and the users & groups should be retrieved from the database for authentication.
How can I do this ? Any clear-cut steps ?
Where can I find them in documentation ?
Please help me...Urgent !!

I found it in
Weblogic Administration Console Home -> Summary of Security Realms->myrealm->Providers.
Click on new Authentication provider button-> you will see 'TrustServiceIdentityAsserter' as one of the types.

Wildcard certifications in Weblogic 5.1,SP8

Has anyone had success in using Thawte's wildcard SSL certificates which are supposed to work with weblogic and allow for multiple sub domains? We have many subdomains running from one weblogic instance that is also clustered across several servers tied to 1 virtual IP address for load balancing. Basically, any advice on using and obtaining SSL certs INEXPENSIVELY to support many subdomains would be appreciated.

Pratik Chatterjee wrote:
Hi,
We are using weblogic connection pool for Oracle 8i databases. For some reason, if the database goes down for only a few hours (after which it becomes available again), then the connection pool automatically refreshes all its connections. As a result our java applications get data normally after the database is back up.
However, we had a very long period of database down (about 24 hours) in production recently and finally when the database became available then we noticed that our java applications were not getting data from the database. Apparently weblogic server did NOT refresh its connections in pool (it seems that after a long period of databse down, the server gave up and did not attempt to refresh connections). We just restarted the weblogic servers in production and that resolved the issue. If you encountered similar issues in the past (with WEblogic 5.1 sp8) and happen to know the resolution then please let us know.
Also, someone in our company reported that if the database servers are down when the weblogic servers are started then weblogic does not create the connection pool at all. As a result if the database became available some time after the weblogic server started, then the java applications didn't get data (even after the DB because available). Again, if you know about this issue and the resolution, please let us know.
Thanks,
PratikHi. If the pool is defined with an initial capacity > 0, then when weblogic starts up,
if it can't create that minimum number of connections, then the pool will not be created
at all. If the initial capacity is zero, then the pool will be created whether or not
the DBMS is up. Once a pool exists, if it needs a connection it will try to create one
and will throw an exception to the application if it can't. Do you have test-connections-on-reserve
set? You should. That would always ensure you get a good connection if it's possible to
provide one.
Joe

Weblogic security authentication; question to interact with the realm

Hi, I have a quick question about weblogic security authentication....
We are using weblogic 81sp3. We have user-group info in an Novell eDirectory LDAP server.
Currently, a Novell Authenticator provider is configured under : Security > Realms > myRealm > Providers > Authentication This tells Weblogic from where to get the user and groups. Weblogic caches this information of the logged on users for certain time ( example : 60 secs ) after which it cleans the cache for all inactive users. We want to interact with the Weblogic cache. Add more user profile information to this cache and use it in our application .
Does somebody know how to programmatically interact with Weblogic user-group cache - read , write , update and delete user-group info in cache and control time to live for the cache ?

already checked
TTLCache class which weblogic provides. But they seem to depracetd it
help ?

Weblogic security: coping URL into other tab

Hi,
We have two Weblogic servers on two phisically different locations.
First of them, WLS A, have perfect security. When you login into any application that is deployed on it, and try:
- copy URL into another tab or browser window, you are getting returned at login page
- when you close browser (without logout), and try to start application from history, you are getting login page, again
So, URL that you have when you enter the application is absolutely useless. Closing the browser, or tab with application have practicaly same meaning as logout.
Second of them, WLS B, have not that security. When you login into any application that is deployed on it, and:
- copy URL into another tab or browser window, you are getting application without need to login! So that URL can be very dangerous, because it is possible to misuse it, if the user don't make logout
- closing browser without logout: it is possible to find out the URL in history and go back into application without login!
It is obvious that the problem is some setting on weblogic server. We tried to compare the settings on WLS A and WLS B but we have not found the setting that we have search for. The programmer that have found and set that property on WLS A working not more in our company.
Can anybody help, we will be very greatful!
Thanks,

Hi,
The authenticate method would take the user and the password details from the environment
(env) that is passed and after successful authentication would populate the subject with
the principals (i.e user, group the user belongs to ..)
It should work with any user that is defined in the WLS not just weblogic/weblogic.
Do you have any other users defined and which group do they belong to?
Vimala
Khalid Rizvi wrote:
I am playing (learning) with weblogic.security.auth.login.UsernamePasswordLoginModule
as a LoginModule using JAAS based authentication. Surprisingly, the only userid
and password combination acceptable is uid=weblogic, pw=weblogic combination.
I went through and looked at the example code under
http://e-docs.bea.com/wls/docs70/security/cli_apps.html#1042212. I found that
the UsernamePasswordLoginModule.login calls into
if (url != null) {
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
try {
Authenticate.authenticate(env, subject);
Seems like UsernamePasswordLoginModule only is a router, as it instantiates an
instance of Environemt using the userid and password and passes this Environemtn
instance (env) to Authenticate.authenticate along with the empty Subject instance.
I read about that the Subject instance will be filled in with Principals by the
WL Server.
My question is that firstly,
1. As Authenticate.authenticate is not passed in the uid and pw, will it pick
those from the env?
2. Secondly, why does it only accept uid=weblogic & pw=weblogic.
I will appreciate if some one can put me in the right direction.
Khalid R. Rizvi
508-641-1192
[email protected]

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?

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

OWSM security for a OSB service- authenticate from weblogic security realms

Hello,
I have a requirement to add security to a OSB service.
The user details are configured in weblogic security realms. lets say there are ten different users.
I need to protect my osb service using OWSM policy & the policy should be configured to authenticate the user from realms.
I am new to OWSM & wondering if this is possible?
Can the experts please direct me to any docs or steps?
Thanks
Ganesh

Hi,
Thanks for the links.
I followed the blog and configured it using oracle/wss_username_token_service_policy.
Now my requirement is to send the username,password from proxy to business and to the BPEL. (the bpel needs this username /password & and in header)
The issue I am facing is the proxy service is not sending the soap header details to business service.
I dont want to make the proxy as passthrough. (ie set Process WS-Security Header to NO)
I have to authorize on proxy level and then send the same credential details to business service?
So the question is, how can I retrieve the header after osb process it?
Can anyone please help me here?
Thanks
Ganesh

Oracle Application Express (APEX) and WebLogic Security

Hi,
Has anyone tried integrating Oracle APEX (custom authentication) with WebLogic Security as the user store?
Thanks
Joel

Hi
Depending on your architecture - APEX in EBS database - or APEX in it's own database instance you're going to have to change a couple of things.
Most importantly - EBS R12 has removed MOd-PLSQL from the Apps menus and from the HTTP listener.
You will need another HTTP listener - Apache with mod-plsql or Database R11 with Embedded Plsql Gateway - EPG.
Second the way that APEX is called from EBS using the Web PLSQL functions in EBS menus is no longer supported in R12.
Check out https://sites.google.com/a/popay.be/apex-on-apps/apps - follow the contacts there - they have also developed a Java utility to call APEX from EBS R12.
In short - depsite Oracle's 'statement of direction' to move away from mod-plsql and removing this from EBS R12 (just what motivates this wierd thinking???)- APEX is still the most flexible and cost-effective means to extend EBS functionality - especially in reporting - and it works just fine in R12.
Good luck
Mike

IPlanet 4.0 and Weblogic 5.10 SP8

I'm using iPlanet 4.0 as a web server and Weblogic 5.10 SP8 as an application server.
Everything is OK when the line "weblogic.httpd.enable=true" is written in the
weblogic.properties file.
When I replace "true" by "false", it declares an error :
Error 403--Forbidden
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization
will not help
and the request SHOULD NOT be repeated. If the request method was not HEAD and
the server
wishes to make public why the request has not been fulfilled, it SHOULD describe
the reason for
the refusal in the entity. This status code is commonly used when the server
does not wish to
reveal exactly why the request has been refused, or when no other response is
applicable.
Is it possible to put weblogic.httpd.enable=false to use Weblogic without its
HTTP Server, and only as an application server ?

The certification was recently completed. It is in the process of being
placed on the web site. At that point, it will be officially supported.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Venkat K" <[email protected]> wrote in message
news:399035f4$[email protected]..
Hello,
Is the NSAPI plugin provided with Weblogic 5.1 Server compatible with
iPlanet 4.1? The Weblogic documentation doesn't seem to be clear to me on
this one. We plan to run in this setup on Solaris 8.
Any details on this are appreciated.
Thanks in advance and Best Regards,
Venkat K.

WebLogic Security in sp8

Similar Messages

Maybe you are looking for