WLS 7.0 Active Directory authenticator - problems starting managed server (Solaris 8)
Has anyone managed to setup a WLS 7.0 Active Directory authenticator and booted
a managed server using the node manager? I can boot the server without the AD
authenticator and I can also boot the server using a script and successfully authenticate
through AD. My AD control flag is set to OPTIONAL and I have also setup a default
authenticator to boot weblogic - the control flag here is set to SUFFICIENT. This
configuration works fine with weblogic running on W2K, but not on Solaris (it
looks like the control flag is being ignored). Errors as follows
####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01> <main>
<kernel identity> <> <000000> <FileLo
gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000415> <System
has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000416> <Using e
ffective file descriptor limit of: 1,024 open sockets/files.>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000418> <Allocat
ing: 3 POSIX reader threads>
####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine> <server01>
<main> <kernel identity> <> <0003
64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
Problem instantiating
Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
thrown by the getAttribute method of the Dynam
icMBean for the attribute Credential>
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine> <server01>
<main> <kernel identity> <> <000
342> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
instantiating Authentication Providerjavax.management.
RuntimeOperationsException: RuntimeException thrown by the getAttribute method
of the DynamicMBean for the attribute Credential
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Solved the problem. The 'domain root' directory specified in the remote start configuration,
must contain a copy of the file 'SerializedSystemIni.dat' that was created along
with the domain, in order to boot when an AD authenticator is configured. If an
AD authenticator is not configured, no file is required. This was not a platform
specific issue; on Win2K I had configured the 'domain root' remote start parameter
to point to an existing domain root and not a new directory.
"Andrew Walker" <[email protected]> wrote:
>
Has anyone managed to setup a WLS 7.0 Active Directory authenticator
and booted
a managed server using the node manager? I can boot the server without
the AD
authenticator and I can also boot the server using a script and successfully
authenticate
through AD. My AD control flag is set to OPTIONAL and I have also setup
a default
authenticator to boot weblogic - the control flag here is set to SUFFICIENT.
This
configuration works fine with weblogic running on W2K, but not on Solaris
(it
looks like the control flag is being ignored). Errors as follows
####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01>
<main>
<kernel identity> <> <000000> <FileLo
gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000415> <System
has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000416> <Using e
ffective file descriptor limit of: 1,024 open sockets/files.>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000418> <Allocat
ing: 3 POSIX reader threads>
####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine>
<server01>
<main> <kernel identity> <> <0003
64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
Problem instantiating
Authentication Providerjavax.management.RuntimeOperationsException:
RuntimeException
thrown by the getAttribute method of the Dynam
icMBean for the attribute Credential>
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of
the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine>
<server01>
<main> <kernel identity> <> <000
342> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.security.service.SecurityServiceRuntimeException:
Problem
instantiating Authentication Providerjavax.management.
RuntimeOperationsException: RuntimeException thrown by the getAttribute
method
of the DynamicMBean for the attribute Credential
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of
the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Similar Messages
-
Active Directory - Authentication Problem
Hi Guys,
I'm seeing something really weird in my Environment.
For example, we have two users as example below in our Active Directory:
jonesp - Paul Jones
jonesph - Phillip Jones
These users can't login into any Mac connected in Active Directory, on PCs the login goes fine.
But when I renamed the login jonesp to jonespa, both users can login in the Macs.
Anyone have this issue too? There is a KB telling about this behavior?
This happens on Macs running 10.7.* and 10.8.*.
ThanksSorry CT,
The problem isn't with Active Directory, this only happens on Macs.
The problem doesn't happens with Windows and Linux, only on Macs.
Anyway thanks for your help.
Regards -
Problem starting managed server in Cluster
Hi,
I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
at weblogic.Server.main(Server.java:67)
Could you pl tell the reason of this error?
Thanks in advance
Hi,
Can anybody help?
Edited by: user10680571 on Dec 4, 2008 4:42 AMThanks David.
During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
<04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
Thanks for your help..... -
Problems starting managed server via nodemanager
Hello,
I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
One hosts the admin server and the seconds hosts a managed server.
I installed the nodemanager on both maschines. They seems to run
normally.
I configured the "Remot Start" for the managed server as mentioned in
the manual. I didn't specified any values in that panel because the
nodemanager uses the same environment as the WLS so these values should
fit the managed WLS too.
But as I try to start the managed server I got the following error
message:
Starting WebLogic Server ....
Child exited
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
So I specified some basic values on the "Remote Start" panel:
BEA_HOME: /www/apps/bea/
ROOT_DIR: /www/apps/bea/wlserver6.1
CLASSPATH:
/www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
No I got this message:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Child exited
What did I wrong?
Has anybody experiences on this problem?
Thanks !
Falko Zurell - Webmaster
Pixelpark AG
Germanynodemanager must be using the old jvm (1.2.2 or whatever comes by
default with 2.8). set up the environment or modify
startNodeManager.sh so that it uses java 1.3.1 that ships with WLS6.1
o.
Falko Zurell <[email protected]> wrote in message news:<[email protected]>...
Hello,
I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
One hosts the admin server and the seconds hosts a managed server.
I installed the nodemanager on both maschines. They seems to run
normally.
I configured the "Remot Start" for the managed server as mentioned in
the manual. I didn't specified any values in that panel because the
nodemanager uses the same environment as the WLS so these values should
fit the managed WLS too.
But as I try to start the managed server I got the following error
message:
Starting WebLogic Server ....
Child exited
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
So I specified some basic values on the "Remote Start" panel:
BEA_HOME: /www/apps/bea/
ROOT_DIR: /www/apps/bea/wlserver6.1
CLASSPATH:
/www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
No I got this message:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Child exited
What did I wrong?
Has anybody experiences on this problem?
Thanks ! -
Problem starting managed server.
Hi,
I have my weblogic server running on UNIX server which has 2 users (UserA and UserB). The Admin server has been started with UserA and the nodemanager with UserB. I have 3 clusters with 2 managed servers each configured in my server. When i start my managed servers from my console 2 clusters (i.e. 4 managed servers have started) but only 1 cluster failed to start throwing the following error.
<Sep 26, 2009 8:41:29 AM GMT> <Error> <Security> <BEA-090033> <Failed to Switch to User UserA java.lang.IllegalArgumentException: Cannot seteuid("UserA"), system error: 'Not owner'
at weblogic.platform.Unix.setEUser0(Native Method)
at weblogic.platform.Unix.setEffectiveUser(Unix.java:49)
at weblogic.t3.srvr.SetUIDManager.switchEffectiveUser(SetUIDManager.java:178)
at weblogic.t3.srvr.SetUIDManager.makeUnprivileged(SetUIDManager.java:104)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:777)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
at weblogic.Server.main(Server.java:32)
.>
Kindly help me with this issue. i wonder why only 1 cluster failed?
Thanks,
Tom
Edited by: user11949331 on Sep 28, 2009 4:24 AMManish, Thanks for your response.
The issue is resolved. The problem seems to be with the privilege.
Whenever i start the Managed server the owner of the Managed server's directory is "UserB" whereas all other files and directories in the domain dir have "UserA" as owner.
So i changed the owner of all the files and dir in the domain directory to "UserA" and tried starting the managed server from command line and it worked.
Thanks,
Tom. -
Problems starting Managed Server on WL6.0 Solaris
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600Hi Falko,
This is not a problem. when you want to add a new managed server to the
admin server, you need to use weblogic console to create that server in the
admin server first, then start the managed server with that name to connect
to the admin server. That is like you have to let the admin server know
there is such a server, then let it join to the Admin server. you can do
that by using the admin console, from left panel, click on Servers -->
"Create a new server" and name it to be "paros", specify the port and IP.
and hit "create". then start the managed server.
Thanks
Yu
"Falko Zurell" <[email protected]> wrote in message
news:[email protected]...
Hi,
I installed a WL6.0 on Solaris 8. Everythings works fine.
I careated a Domain and an additional Server wich is located at a
different machine. As is start this managed server on the other machine
it complains with the following error message:
<Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
Connecting to http://sol23:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: paros not
found
weblogic.management.configuration.ConfigurationException: paros not
found
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
at weblogic.management.Admin.initialize(Admin.java:287)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
In the access-Log of the Admin-Server the following line appears
my IP - - [30/Aug/2001:12:41:13 +0200] "GET
/wl_management_internal2/Bootstrap HTTP/1.0" 404 0
So my question: Where does this "wl_management_internal2" Application
come from?
Do I have to install some special things when I start an Admin-Server?
thanks
Falko Zurell . Webmaster
Pixelpark AG . http://www.pixelpark.com
Rotherstrasse 8 . 10245 Berlin . Germany
phone: + 49 30 5058 - 1963 . fax: -1600 -
Problem starting managed server using Node Manager/WL 7
I have just configured Node Manager for the first time to start a managed server,
following the documentation 'Managing Server Availability with Node Manager'. However
when I attempt to start the managed server from the Administration Console I always
get the following exception:
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <Starting
Server webdevDomain::apps ...>
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <BaseProcessControl:
saving process id of Weblogic Managed server 'apps', pid: 15094>
Starting WebLogic Server...
Connecting to http://198.242.140.49:17043...
<Jul 10, 2002 1:59:32 PM EDT> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:weblogic.management.configuration.ConfigurationException:
Exception encountered connecting to http://198.242.140.49:17043/wl_management_internal2/Bootstrap
- with nested exception:
[java.io.StreamCorruptedException: InputStream does not contain a serialized object]
java.io.StreamCorruptedException: InputStream does not contain a serialized object
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:844)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:163)
at weblogic.management.ManagedServerAdmin.bootstrapLocalServer(ManagedServerAdmin.java:212)
at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:122)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:665)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
But I am able to start the managed server using the startApps.sh script with no problems.
I am running WL 7 on Solaris 2.8. All processes are running on the same host.
Any help is appreciated!
JohnRe-installing WL Server 7.0.0.1 resolved this problem.
- John -
We have the following setup.
CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
administrator. We start CLUSTER3 as a self-managed server and then try and start
CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
1 and 2 we get the following:
D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
03:7001
D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
D:\bea\wlserver6.1>echo off
* To start WebLogic Server, use the password *
* assigned to the system user. The system *
* username and password must also be used to *
* access the WebLogic Server console from a web *
* browser. *
D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
-Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
"-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
r
<20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
Connecting to http://10.0.1.103:7001...
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: The
name of the managed server is same as admin server. The managed server will not
be allowed to start up.
weblogic.management.configuration.ConfigurationException: The name of the manage
d server is same as admin server. The managed server will not be allowed to star
t up.
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
D:\bea\wlserver6.1>goto finish
D:\bea\wlserver6.1>cd config\CLUSTER1
D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
D:\bea\wlserver6.1\config\CLUSTER1>
Many thanks in advance,
Alex Burton
http://www.e-plus.com.au/
Don't start the admin server as managed. Removing
-Dweblogic.management.server...
from the command line should help.
Alex Burton wrote:
> We have the following setup.
> CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
> administrator. We start CLUSTER3 as a self-managed server and then try and start
> CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
> 1 and 2 we get the following:
>
> D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
> 03:7001
>
> D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
>
> D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
>
> D:\bea\wlserver6.1>echo off
>
> ***************************************************
> * To start WebLogic Server, use the password *
> * assigned to the system user. The system *
> * username and password must also be used to *
> * access the WebLogic Server console from a web *
> * browser. *
> ***************************************************
>
> D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
> ".
> ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
> ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
> -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
> "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
> r
> <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
> Enter password to boot WebLogic server:
> Starting WebLogic Server ....
> Connecting to http://10.0.1.103:7001...
> ***************************************************************************
> The WebLogic Server did not start up properly.
> Exception raised: weblogic.management.configuration.ConfigurationException: The
> name of the managed server is same as admin server. The managed server will not
> be allowed to start up.
> weblogic.management.configuration.ConfigurationException: The name of the manage
> d server is same as admin server. The managed server will not be allowed to star
> t up.
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
> ***************************************************************************
>
> D:\bea\wlserver6.1>goto finish
>
> D:\bea\wlserver6.1>cd config\CLUSTER1
>
> D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
>
> D:\bea\wlserver6.1\config\CLUSTER1>
>
> Many thanks in advance,
> Alex Burton
> http://www.e-plus.com.au/
-
Problems starting managed server from admin console WL70 portal
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
-
Problem starting managed server (WL6.1sp2)
I'm trying to staret a managed server, but keep getting errors fetching the
configuration from the admin server?
Right after the first error message, it says"> This condition generally
results when the managed and admin servers are using the same listen address
and port.>"
However, this is not the case here. Any ideas?
The managed server and the admin server uses the same password,
"adminpassword" (yes, this is an internal development system :-)
Here's the error message:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h
".;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=wavetech -Dbe
a.home=C:\bea -Dweblogic.management.password=adminpassword -Dweblogic.Produc
tionModeEnabled=false -Dweblogic.Name=cbfilter -Dweblogic.management.server=
http://192.168.10.31:6001/ -Djava.security.policy=C:\bea\wlserver6.1/lib/web
logic.policy weblogic.Server
Starting WebLogic Server ....
Connecting to http://192.168.10.31:6001/...
<08-03-2002 14:22:49 CET> <Emergency> <Configuration Management> <Errors
detected attempting to connect to admin server at http://192.168.10.31:6001/
during initialization of managed server ( 192.168.10.85:80 ). The reported
error was: < weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
> This condition generally results when the managed and admin servers are
using the same listen address and port.>
<08-03-2002 14:22:49 CET> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>cd config\wavetech
C:\bea\wlserver6.1\config\wavetech>ENDLOCALI'm trying to staret a managed server, but keep getting errors fetching the
configuration from the admin server?
Right after the first error message, it says"> This condition generally
results when the managed and admin servers are using the same listen address
and port.>"
However, this is not the case here. Any ideas?
The managed server and the admin server uses the same password,
"adminpassword" (yes, this is an internal development system :-)
Here's the error message:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h
".;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=wavetech -Dbe
a.home=C:\bea -Dweblogic.management.password=adminpassword -Dweblogic.Produc
tionModeEnabled=false -Dweblogic.Name=cbfilter -Dweblogic.management.server=
http://192.168.10.31:6001/ -Djava.security.policy=C:\bea\wlserver6.1/lib/web
logic.policy weblogic.Server
Starting WebLogic Server ....
Connecting to http://192.168.10.31:6001/...
<08-03-2002 14:22:49 CET> <Emergency> <Configuration Management> <Errors
detected attempting to connect to admin server at http://192.168.10.31:6001/
during initialization of managed server ( 192.168.10.85:80 ). The reported
error was: < weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
> This condition generally results when the managed and admin servers are
using the same listen address and port.>
<08-03-2002 14:22:49 CET> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:988)
at weblogic.management.Admin.start(Admin.java:363)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
C:\bea\wlserver6.1>cd config\wavetech
C:\bea\wlserver6.1\config\wavetech>ENDLOCAL -
I have a java application (SSO via SAML2) that uses Weblogic as a Identity Service Provider. All works well using users created directly in Weblogic. However, I need to add support for Active Directory. So, as per documentation:
- I defined an Active Directory Authentication provider
- changed it's order in the Authentication Providers list so that it comes first
- set the control flag to SUFFICIENT and configured the Provider Specific; here's the concerned part in config.xml:
<sec:authentication-provider xsi:type="wls:active-directory-authenticatorType">
<sec:name>MyOwnADAuthenticator</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:propagate-cause-for-login-exception>true</wls:propagate-cause-for-login-exception>
<wls:host>10.20.150.4</wls:host>
<wls:port>5000</wls:port>
<wls:ssl-enabled>false</wls:ssl-enabled>
<wls:principal>CN=tadmin,CN=wl,DC=at,DC=com</wls:principal>
<wls:user-base-dn>CN=wl,DC=at,DC=com</wls:user-base-dn>
<wls:credential-encrypted>{AES}deleted</wls:credential-encrypted>
<wls:cache-enabled>false</wls:cache-enabled>
<wls:group-base-dn>CN=wl,DC=at,DC=com</wls:group-base-dn>
</sec:authentication-provider>
I configured a AD LDS instance(Active Directory Lightweight Directory Services) on a Windows Server 2008 R2. I created users and one admin user "tadmin" which was added to Administrators members. I also made sure to set msDS-UserAccountDisabled property to FALSE.
After restarting Weblogic I can see that the AD LDS's users and groups are correctly fetched in Weblogic. But, when I try to connect with my application, using Username:tadmin and Password:<...> it does not work.
Here's what I see in the log file:
<BEA-000000> <LDAP Atn Login username: tadmin>
<BEA-000000> <authenticate user:tadmin>
<BEA-000000> <getConnection return conn:LDAPConnection {ldaps://10.20.150.4:5000 ldapVersion:3 bindDN:"CN=tadmin,CN=wl,DC=at,DC=com"}>
<BEA-000000> <getDNForUser search("CN=wl,DC=at,DC=com", "(&(&(cn=tadmin)(objectclass=user))(!(userAccountControl:1.2.840.113556.1.4.803:=2)))", base DN & below)>
<BEA-000000> <DN for user tadmin: null>
<BEA-000000> <returnConnection conn:LDAPConnection {ldaps://10.20.150.4:5000 ldapVersion:3 bindDN:"CN=tadmin,CN=wl,DC=at,DC=com"}>
<BEA-000000> <getConnection return conn:LDAPConnection {ldaps://10.20.150.4:5000 ldapVersion:3 bindDN:"CN=tadmin,CN=wl,DC=at,DC=com"}>
<BEA-000000> <getDNForUser search("CN=wl,DC=at,DC=com", "(&(&(cn=tadmin)(objectclass=user))(!(userAccountControl:1.2.840.113556.1.4.803:=2)))", base DN & below)>
<BEA-000000> <DN for user tadmin: null>
<BEA-000000> <returnConnection conn:LDAPConnection {ldaps://10.20.150.4:5000 ldapVersion:3 bindDN:"CN=tadmin,CN=wl,DC=at,DC=com"}>
<BEA-000000> <javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User tadmin denied
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:229)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
So, I tried to look why do I have: <DN for user tadmin: null>. Using Apache Directory Studio I reproduced the ldap search request used in Weblogic and, sure enough, I get no results. But, changing the filter to only "(&(cn=tadmin)(objectclass=user))" (NOTICE, no userAccountControl), it works; here's the result from Apache Directory Studio:
#!SEARCH REQUEST (145) OK
#!CONNECTION ldap://10.20.150.4:5000
#!DATE 2014-01-23T14:52:09.324
# LDAP URL : ldap://10.20.150.4:5000/CN=wl,DC=at,DC=com?objectClass?sub?(&(cn=tadmin)(objectclass=user))
# command line : ldapsearch -H ldap://10.20.150.4:5000 -x -D "[email protected]" -W -b "CN=wl,DC=at,DC=com" -s sub -a always -z 1000 "(&(cn=tadmin)(objectclass=user))" "objectClass"
# baseObject : CN=wl,DC=at,DC=com
# scope : wholeSubtree (2)
# derefAliases : derefAlways (3)
# sizeLimit : 1000
# timeLimit : 0
# typesOnly : False
# filter : (&(cn=tadmin)(objectclass=user))
# attributes : objectClass
#!SEARCH RESULT DONE (145) OK
#!CONNECTION ldap://10.20.150.4:5000
#!DATE 2014-01-23T14:52:09.356
# numEntries : 1
(the "[email protected]" is defined as userPrincipalName in the tadmin user on AD LDS)
As you can see, "# numEntries : 1" (and I can see as result the entry "CN=tadmin,CN=wl,DC=at,DC=com" in Apache Directory Studio's interface); if I add the userAccountControl filter I get 0.
I've read that the AD LDS does not use userAccountControl but "uses several individual attributes to hold the information that is contained in the flags of the userAccountControl attribute"; among those attributes is msDS-UserAccountDisabled which, as I said, I already set to FALSE.
So, my question is, how do I make it work? Why do I have "<DN for user tadmin: null>" ? Is it the userAccountControl ? If it is, do I need to do some other configuration on my AD LDS ? Or, how can I get rid of the userAccountControl filter in Weblogic?
I didn't seem to find it in config files or in the interface: I only have "User From Name Filter: (&(cn=%u)(objectclass=user))", there's no userAccountControl.
Another difference I noticed is that, even though in Weblogic I have set ssl-enabled flag to false, in the logs I see ldaps and not ldap ( I'm not looking to setup something production-ready and I don't want SSL for the moment ).
Here are some other things I tried but did not change anything:
- the other "msDS-" attributes were not set so I tried initializing them to some value
- I tried other users defined in AD LDS, not tadmin
- in Weblogic I added users that were imported from AD LDS in Roles and Policies> Realm Roles > Global Roles > Roles > Admin
- I removed all userAccountControl occurrences that I found in xml files in Weblogic (schema.ms.xml, schema.msad2003.xml)
Any thoughts?
Thanks.I managed to narrow it down: the AD LDS does not support the userAccountControl.
Anyone knows how I can configure my Active Directory Authentication Provider in Weblogic so that it does not implicitly use userAccountControl as filter?
<BEA-000000> <getDNForUser search("CN=wl,DC=at,DC=com", "(&(&(cn=tadmin)(objectclass=user))(!(userAccountControl:1.2.840.113556.1.4.803:=2)))", base DN & below)> -
Active Directory Authentication in Weblogic 8.1
Hi,
We want to do authentication from Microsoft Active Directory using weblogic 8.1.
I have created a Active directory and
configured weblogic from console to use it. But it is still not working. Your
help with these question would be highly
appreciated.
1. Is there anyone in group who have tried this before. Please let me know how
to proceed.
2. Is there any tool by which I can get to know the different attribute asked
for configuration in Weblogic?
3. I am not able to login to my application after configuration. Is there any
other way to come to know whether it is working
or not?
There could be plethora of reason but nothing which can come to my mind. Everything
seems to be configured correctly. Here is
portion of my config.xml related with authentication:
<FileRealm Name="wl_default_file_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<Security GuestDisabled="false" Name="vendavo-dev"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true">
<weblogic.security.providers.authentication.DefaultAuthenticator
ControlFlag="SUFFICIENT"
Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authentication.DefaultIdentityAsserter
ActiveTypes="AuthenticatedUser"
Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultRoleMapper
Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultAuthorizer
Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultAdjudicator
Name="Security:Name=myrealmDefaultAdjudicator" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.credentials.DefaultCredentialMapper
Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
<weblogic.management.security.authentication.UserLockoutManager
Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
<weblogic.management.security.Realm
Adjudicator="Security:Name=myrealmDefaultAdjudicator"
AuthenticationProviders="Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter|Security:Name
=myrealmADAuthenticator"
Authorizers="Security:Name=myrealmDefaultAuthorizer"
CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
DefaultRealm="true" DisplayName="myrealm"
Name="Security:Name=myrealm"
RoleMappers="Security:Name=myrealmDefaultRoleMapper"
UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
<weblogic.security.providers.pk.DefaultKeyStore
Name="Security:Name=myrealmDefaultKeyStore" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authentication.ActiveDirectoryAuthenticator
ControlFlag="SUFFICIENT" Credential="{3DES}hvEo4sy7g1E="
DisplayName="ADAuthenticator" FollowReferrals="false"
GroupBaseDN="ou=ou=Groups,dc=devdc,dc=com" Host="venper5"
Name="Security:Name=myrealmADAuthenticator"
Principal="vendev" Realm="Security:Name=myrealm" UserBaseDN="ou=Users,dc=devdc,dc=com"/>
</Security>
First, of all is it possible to use Active Directory authentication in Weblogic
without writing any custom code. If yes, how?
Thanks in advance,
Amit TyagiAmit,
We have successfully used WLS 8.1 sp1 with AD - but not without our share of ups
and downs though.
|
|
1) First, make sure you are sending right LDAP queries to AD. To verify this,
we used free 3rd party LDAP browser from Softerra. There is also java based free
browser from Univ of Michigan. Personally, I like Softerra's LDAP browser better.
Play with your LDAP settings using this and make sure AD is returning the right
data.
|
2) AD has some default settings that makes it return only the top 1000 users.
Use ntdsutil.exe to modify these default settings
|
3) AD needs to have the right set of users and groups. To configure this, refer
to WLS docs. This is very well documented in WLS docs. Also refer to this article
http://dev2dev.bea.com/products/wlportal/whitepapers/wlp70_MSADS.jsp as additional
reference
|
4) Also, there are some bugs with 8.1 portal sp1 and AD. It cannot take more than
one Authentication provider. sp2 is supposed to have fixed it. For sp1 we used
another product AD/AM (AD in Application Mode) in combination with MIIS server.
But if you are using sp2, you shouldn't be worry about this.
|
5) In your providers, you might want to get rid of the DefaultAuthentication provider,
once you are able to establish a connection with your ActiveDirectoryAuthentication
provider. The DefaultAuthentication provider causes some problems and does not
let ActiveDirectoryAuthentication provider to behave properly. We haven't fully
investgated the root of this prob. When we deleted DefaultAuthentication provider,
everything worked normally - so we didn't really care that much :-)
|
6) Make sure you have your JAAS options set to OPTIONAL initially and make sure
your are able to authenticate talk to your AD.
|
These are the ones I could think of. Hope this helps..
Regards,
Anant
"Amit" <[email protected]> wrote:
>
Hi,
We want to do authentication from Microsoft Active Directory using weblogic
8.1.
I have created a Active directory and
configured weblogic from console to use it. But it is still not working.
Your
help with these question would be highly
appreciated.
1. Is there anyone in group who have tried this before. Please let me
know how
to proceed.
2. Is there any tool by which I can get to know the different attribute
asked
for configuration in Weblogic?
3. I am not able to login to my application after configuration. Is there
any
other way to come to know whether it is working
or not?
There could be plethora of reason but nothing which can come to my mind.
Everything
seems to be configured correctly. Here is
portion of my config.xml related with authentication:
<FileRealm Name="wl_default_file_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<Security GuestDisabled="false" Name="vendavo-dev"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true">
<weblogic.security.providers.authentication.DefaultAuthenticator
ControlFlag="SUFFICIENT"
Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authentication.DefaultIdentityAsserter
ActiveTypes="AuthenticatedUser"
Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultRoleMapper
Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultAuthorizer
Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultAdjudicator
Name="Security:Name=myrealmDefaultAdjudicator" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.credentials.DefaultCredentialMapper
Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
<weblogic.management.security.authentication.UserLockoutManager
Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
<weblogic.management.security.Realm
Adjudicator="Security:Name=myrealmDefaultAdjudicator"
AuthenticationProviders="Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter|Security:Name
=myrealmADAuthenticator"
Authorizers="Security:Name=myrealmDefaultAuthorizer"
CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
DefaultRealm="true" DisplayName="myrealm"
Name="Security:Name=myrealm"
RoleMappers="Security:Name=myrealmDefaultRoleMapper"
UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
<weblogic.security.providers.pk.DefaultKeyStore
Name="Security:Name=myrealmDefaultKeyStore" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authentication.ActiveDirectoryAuthenticator
ControlFlag="SUFFICIENT" Credential="{3DES}hvEo4sy7g1E="
DisplayName="ADAuthenticator" FollowReferrals="false"
GroupBaseDN="ou=ou=Groups,dc=devdc,dc=com" Host="venper5"
Name="Security:Name=myrealmADAuthenticator"
Principal="vendev" Realm="Security:Name=myrealm" UserBaseDN="ou=Users,dc=devdc,dc=com"/>
</Security>
First, of all is it possible to use Active Directory authentication in
Weblogic
without writing any custom code. If yes, how?
Thanks in advance,
Amit Tyagi -
Unable to find user list in Active Directory Authenticator
Hi all,
I am using weblogic 10.3 and want to configure ActiveDirectory Authenticator for my weblogic application. We have one managed srever under admin server . I have configured a Active Directory Authenticator named "ADAuthenticator" and made following changes as per the below values:
I set the control flag to "OPTIONAL" .
Security Realms-->myrealm-->Providers-->ADAuthenticator-->Provider Specific
UserName Attribute : ServiceBEA
Principal : ServiceBEA
Host : xxxxxx
User Search Scope : subtree
Group From Name Filter : (&(ServiceBEA=%g)(objectclass=group))
Credential : xxxxxx
Confirm Credential : xxxxxx
User From Name Filter : (&(ServiceBEA=%u)(objectclass=user))
Static Group Name Attribute : ServiceBEA
User Base DN : values provided as per requirement
Port : 389
User Object Class : user
Use Retrieved User Name as Principal : checked
Group Base DN : same values as per User Base DN
Static Group Object Class : group
Group Membership Searching : unlimited
Max Group Membership Search Level : 0
These are my AD settings. After doing this i click on save and then activate changes and then restarted the admin server.
But the problem is when i login to weblogic console to check the user list under "User and Group" i am unble to find any Active Directory users.
I don't know where i made the mistake. Can some make me out of this trouble.
Any help is highly appreciated.
Thanks in advance !Hi Sean,
Actually we have already a Active Directory with username "ServiceBEA" in our windows server. So i used this "ServiceBEA" as UserName Attribute in weblogic console while creating a Active Directory Authenticator.
You mean to say that we should go for "sAMAccountName" or what? If that is the case then i have also tested with following values, but still no luck.
UserName Attribute : sAMAccountName
Principal : ServiceBEA
Host : xxxxxx
User Search Scope : subtree
Group From Name Filter : (&(sAMAccountName=%g)(objectclass=group))
Credential : xxxxxx
Confirm Credential : xxxxxx
User From Name Filter : (&(sAMAccountName=%u)(objectclass=user))
Static Group Name Attribute : sAMAccountName
User Base DN : values provided as per requirement
Port : 389
User Object Class : user
Use Retrieved User Name as Principal : checked
Group Base DN : same values as per User Base DN
Static Group Object Class : group
Group Membership Searching : unlimited
Max Group Membership Search Level : 0
Please advise what to be place in case of User Name Attribute.
Any help is highly appreciated.
Thanks in advance ! -
Active Directory integration problem, Bind AC and OD
Hi.
I'm trying to set an Open Directory as "connect to a Directory System" because I have a windows 2000 server with Active Directory. But i have a problem when i click on "open directory Access", Access Directory appear and I select Active Directory.
xxx.yyy is the server with active directory, with its admin and its password. but i cant Bind it and an error always appear.
can you help me?
what's "active directory domain"?is it xxx.yyy?
and what's "computer ID"?
Are there others parameters to set for example in DNS or other?
help help helpWhat are you trying to achieve by doing this?
Got to http://www.afp548.com/ and serach for AD-OD integration.
http://www.afp548.com/article.php?story=20051202151540574 -
BO XI 3.1 : Active Directory Authentication failed to get the Active Directory groups
Dear all
In our environment, there are 2 domain (domain A and B); it works well all the time. Today, all the user belong to domain A are not logi n; for user in domain B, all of them can log in but BO server response is very slowly. and there is error message popup when opening Webi report for domain B user. Below are the error message:
" Active Directory Authentication failed to get the Active Directory groups for the account with ID:XXXX; pls make sure this account is valid and belongs to an accessible domain"
Anyone has encountered similar issue?
BO version: BO XI 3.1 SP5
Authenticate: Windows AD
Thanks and RegardsPlease get in touch with your AD team and verify if there are any changes applied to the domain controller and there are no network issues.
Also since this is a multi domain, make sure you have 2 way transitive forest trust as mentioned in SAP Note : 1323391 and FQDN for Directory servers are maintained in registry as per 1199995
http://service.sap.com/sap/support/notes/1323391
http://service.sap.com/sap/support/notes/1199995
-Ambarish-
Maybe you are looking for
-
How can I transfer some photos from PE11 to be saved on my new IPad?
How can I transfer some photos from PE11 to be saved on my new IPad? I know I can use Adobe Revel but that relies on an Internet connection. The person I wish to show the photos do not have internet connection.
-
Hello, it seems that since I installed OS X 10.8 I need to visit these forums more often... Ok, the problem is just the following screenshot... I've tried restarting, plugging an external HD (with the proper format), but I don't know how to handle th
-
Ipad: photo slide show with music problem.
Using the ipad, looking at my photo's, I select a photo, select slide show and knowing that I have already set the play music with slide show, I then press the Airplay icon. Seconds later the slide show starts on the Apple TV, but there is no music.
-
Questions on HP Photosmart D 5160
hi, in a couple of day we will receive a new mac book pro delivered with a free hp photosmart d 5160. 1) do i need to install additional hp drivers. (on the hp website there are beta drivers v. 9.7 for the 5100 series). 2) do i only need these driver
-
WD Smartware Compatible Mac?
I am borrowing a 500GB WD Smartware external HD from my friend because I am backing up my computer. I have opened the external HD and viewed the files on me iMac before and there was maybe about 2 GBs worth of files on it. Now Today I try and open hi