Settting embedded LDAP password using WLST

Hi All,
I have a requirement where I need to automate some setup on weblogic server. As part of these scripts, I need to set the embedded ldap password using WLST . I tried recording the actions through Admin console. But, I wasn't able to use the generated script for the same. Any pointers on this would be really helpful.

Do you mean you need to change a users password in embeded LDAP? If so here's the link Configuring Existing WebLogic Domains - 12c Release 1 (12.1.1) look for
Changing a Password

Similar Messages

Embedded LDAP password issue in Weblogic 7

Is this normal? Seems odd to me...
After installing weblogic 7 using the wizard and giving a new password other than "weblogic" for the "weblogic" user, and after using boot.properties to get an encrypted version, the embedded LDAP servers for both admin and managed servers do not seem to have the new password.
If I try to use JNDI to get a JMX MBean Home on the managed server, I get an exception saying I have the wrong password for "weblogic".
After using the admin console to change the password to the value it supposedly already has, the embedded LDAP servers for both the admin and consumer have a new (encrypted but presumably correct) password but the JNDI call still fails.
After undeploying and redeploying the relevant web application the JNDI call succeeds.
Killing and restarting the admin and managed servers does not seem to be relevant. Setting the read replica on startup flag doesn't seem to help. This is mostly on testing on the petstore example. This may be relevant since at some point BEA changed the user/password for it to "weblogic/weblogic"
QUESTIONS:
Does anybody understand why this is happening?
Any ideas for fixes that avoid bouncing and redeployment?
---Paul O

Never mind...
I think I have solved this with the help of an LDAP browser and a custom JNDI/JMX password tester.
One problem that threw me off was that changes that were thought to be happening in testing were not really "taking"
due to precompilation of JSPs. I had thought that redeploying made the correct password "take" but actually it was helping changes in the code to take effect. Another problem that I believe but have yet to verify contributed to the confusion and a related failure to log is that once a user is rejected repeatedly, Weblogic locks the account for a half hour by default.
The bottom line is it really pays to use instruments that tell you what the actual state of affairs is as conjectures are often wrong for unexpected reasons.
---Paul O
Paul O'Rorke wrote:
Is this normal? Seems odd to me...
After installing weblogic 7 using the wizard and giving a new password
other than "weblogic" for the "weblogic" user, and after using
boot.properties to get an encrypted version, the embedded LDAP servers
for both admin and managed servers do not seem to have the new password.
If I try to use JNDI to get a JMX MBean Home on the managed server, I
get an exception saying I have the wrong password for "weblogic".
After using the admin console to change the password to the value it
supposedly already has, the embedded LDAP servers for both the admin and
consumer have a new (encrypted but presumably correct) password but the
JNDI call still fails.
After undeploying and redeploying the relevant web application the JNDI
call succeeds.
Killing and restarting the admin and managed servers does not seem to be
relevant. Setting the read replica on startup flag doesn't seem to
help. This is mostly on testing on the petstore example. This may be
relevant since at some point BEA changed the user/password for it to
"weblogic/weblogic"
QUESTIONS:
Does anybody understand why this is happening?
Any ideas for fixes that avoid bouncing and redeployment?
---Paul O

Error in change LDAP password

Hi,
Can anybody help me out in this .
I want to change LDAP password using follows command:
modifyldapbindpasswd.exe -genpasswdfile test_file.xml
But there is a error appear: No installation directory specified.
Please reply me with possible solution .
Regards,
keikey.

Thanks for Mahendra's help!
When I use the follow command,another error appears:
C:\oracle\oam\idserver\identity\oblix\tools\modbinpasswd>modifyldapbindpasswd.exe -i c:\oracle\oam\idserver\identity -c is -t all -x ***** -y *****
Error = The specified procedure could not be found.
Symbol=oblxkInitcap
Error = The specified procedure could not be found.
Symbol=obslxcfcb
Error = The specified procedure could not be found.
Symbol=obslxcfob
Error = The specified procedure could not be found.
Symbol=obslxcfrb
Error = The specified procedure could not be found.
Symbol=oblfvinit
Error = The specified procedure could not be found.
Symbol=oblxldini
Error = The specified procedure could not be found.
Symbol=oblxlgsz
Error =The specified procedure could not be found.
Symbol=obslsta2e
Error = The specified procedure could not be found.
Symbol=obslste2a
Error = The specified procedure could not be found.
Symbol=oblxlfrd
Error = The specified procedure could not be found.
Symbol=oblxpendian
Language initialization failed. Please check that the installation directory is correct.
Please reply me with possible solution .
Regards,
keikey.
Edited by: keikey on 2009-10-28 下午6:31

How to change password for a user in WLS 7.0 embedded ldap in code?

I asked the similar question before but don't have an answer yet.
I need to change password for a user in my Java code. Any help will be
appreciated.
Here is my stack trace:
c:\Test>java -classpath . testEmbeddedLdap
attribute: uid
attribute: description
attribute: objectclass
attribute: wlsMemberOf
attribute: sn
attribute: cn
javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient
Access Rights]; remaining name
'uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2872)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2810)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2616)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1374)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDir
Context.java:255)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:172)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:161)
at
javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.
java:146)
at testEmbeddedLdap.main(testEmbeddedLdap.java:30)
Here is my testing code:
<PRE>
import java.util.*;
import javax.naming.*;
import javax.naming.directory.*;
public class testEmbeddedLdap {
public static void main(String[] argv) {
Hashtable env = new Hashtable(11);
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://localhost:7001");
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "uid=myAdministrator, ou=people,
ou=myrealm, dc=mydomain");
env.put(Context.SECURITY_CREDENTIALS, "myAdministrator");
try {
DirContext ctx = new InitialDirContext(env);
String
sUser="uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain";
String sOldPassword="myRegularUser";
String sNewPassword="newpassword";
for (NamingEnumeration ae = ctx.getAttributes(sUser).getAll();
ae.hasMore(); ) {
Attribute attr = (Attribute)ae.next();
System.out.println("attribute: " + attr.getID());
ModificationItem[] mods = new ModificationItem[2];
Attribute mod0 = new BasicAttribute("userpassword",
sOldPassword);
mods[0] = new ModificationItem(DirContext.REMOVE_ATTRIBUTE,
mod0);
Attribute mod1 = new BasicAttribute("userpassword",
sNewPassword);
mods[1] = new ModificationItem(DirContext.ADD_ATTRIBUTE, mod1);
ctx.modifyAttributes(sUser, mods);
ctx.close();
} catch (NamingException e) {
e.printStackTrace();
</PRE>
"Neil Smithline" <[email protected]> wrote in message
news:[email protected]...
Two things. First, I'm not exactly sure what password you are trying to
change. The LDAP server's password or a user's password in the LDAP
server. Second, could you please post a stack trace.
Thanks - Neil
K Wong wrote:
I am using (javax.naming.directory.DirContext.modifyAttributes) to
change
password to our development Weblogic 7.0 embedded LDAP.
I login as the system administrator (a user in the administratorsgroup),
but always gets the javax.naming.NoPermissionException - InsufficientAccess
Rights.
What user should I use? Any help will be appreciated.

Hai,
This condition based execution requires - javascript coding.
In miscelleaneous tools bar, you have an option of SCRIPT_ITEM writer tool, drag the tool into your WAD layout, and select the properties , choose the editor option and paste your coding. that's it.
Alternate option :
in your web application design layout , you will fine XHTML coding editor , there you need to write coding and execute the same.
Hope this will help to you.
Assign Points if its really useful.
Cheers !!!
Bye
Regards,
Giri

How many entries is embedded LDAP of weblogic 8.1 capable to store ? let's assume we use default LDAP schema being defined in schema.core.xml

"ming qin" <[email protected]> wrote in message news:[email protected]..
I would like to have entries as users.There are a few issues that arise as the number of users increases. The
first is management
of all these users. Will you be able to load/update/manage all of the users
via the WLS console?
You can certainly use external LDAP tools to manage the data in the WLS
embedded LDAP
server, but using an external LDAP server may offer better tools for
management than those
offered in WLS.
The second is performance. Since the ldap server embedded within WLS uses
in-memory
indices, the time to load the indices and the memory required for storing
them increases as
the number of users increases. 20-50K seems to have reasonable performance.
The last is extensibility. The WLS default authenticator stores user,
description, and password.
You may have different requirements and want to store additional
information.

What is the WLS 7.0 embedded ldap admin account and password?

I am using (javax.naming.directory.DirContext.modifyAttributes) to change
password to our development Weblogic 7.0 embedded LDAP.
I login as the system administrator (a user in the administrators group),
but always gets the javax.naming.NoPermissionException - Insufficient Access
Rights.
What user should I use? Any help will be appreciated.

I need to change password for a user. Any help will be appreciated.
Here is my stack trace:
c:\Test>java -classpath . testEmbeddedLdap
attribute: uid
attribute: description
attribute: objectclass
attribute: wlsMemberOf
attribute: sn
attribute: cn
javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient
Access Rights]; remaining name
'uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2872)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2810)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2616)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1374)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDir
Context.java:255)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:172)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:161)
at
javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.
java:146)
at testEmbeddedLdap.main(testEmbeddedLdap.java:30)
Here is my testing code:
<PRE>
import java.util.*;
import javax.naming.*;
import javax.naming.directory.*;
public class testEmbeddedLdap {
public static void main(String[] argv) {
Hashtable env = new Hashtable(11);
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://localhost:7001");
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "uid=myAdministrator, ou=people,
ou=myrealm, dc=mydomain");
env.put(Context.SECURITY_CREDENTIALS, "myAdministrator");
try {
DirContext ctx = new InitialDirContext(env);
String
sUser="uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain";
String sOldPassword="myRegularUser";
String sNewPassword="newpassword";
for (NamingEnumeration ae = ctx.getAttributes(sUser).getAll();
ae.hasMore(); ) {
Attribute attr = (Attribute)ae.next();
System.out.println("attribute: " + attr.getID());
ModificationItem[] mods = new ModificationItem[2];
Attribute mod0 = new BasicAttribute("userpassword",
sOldPassword);
mods[0] = new ModificationItem(DirContext.REMOVE_ATTRIBUTE,
mod0);
Attribute mod1 = new BasicAttribute("userpassword",
sNewPassword);
mods[1] = new ModificationItem(DirContext.ADD_ATTRIBUTE, mod1);
ctx.modifyAttributes(sUser, mods);
ctx.close();
} catch (NamingException e) {
e.printStackTrace();
</PRE>
"Neil Smithline" <[email protected]> wrote in message
news:[email protected]...
Two things. First, I'm not exactly sure what password you are trying to
change. The LDAP server's password or a user's password in the LDAP
server. Second, could you please post a stack trace.
Thanks - Neil
K Wong wrote:
I am using (javax.naming.directory.DirContext.modifyAttributes) to
change
password to our development Weblogic 7.0 embedded LDAP.
I login as the system administrator (a user in the administratorsgroup),
but always gets the javax.naming.NoPermissionException - InsufficientAccess
Rights.
What user should I use? Any help will be appreciated.

Can we detect the user first time he logs in ( appln uses embedded ldap )

Hi,
We are using weblogic embedded ldap for authentication in our application
The first time the user logs in to our applicaiton, we need to detect he is log-in the first time,
so take him to change password page.
Can we do like that ?
Regards,
Harsha
Edited by: harsha.karthigai on Aug 28, 2009 5:50 AM

Hi,
By default when you open a report it displays the report exactly as it was last saved. So even if you user views the report
drills down
then closes the report without saving
then views the report immediately
the report will open in its original state. There is no setting which can be amended to change this. It is possible to write your own viewer but that would be a significant piece of work
Regards
Alan

How to configure human workflow using embedded ldap in standalone weblogic

I am trying to use embedded ldap to select users for a human workflow. I have created an application server instance using soa server details but the realm field in human workflow remains empty.
Please let me know what would be right steps.

Can you provide more details about the context of where this happens? Are you selecting users in the Organization editor in BPM studio? Is this on 11.1.1.3 or 11.1.1.4?

Can I use your Embeded LDAP Server?

Hi,
WebLogic Server 7.0 and 8.1 comes with an embedded LDAP Server?
I have an application that requires iPlanet Directory Server for 7000 entries.
Can I use the embedded LDAP Server to put my own entries and use it?
Regards,
Shanmugavel R P

Are these videos on mozilla.org somewhere? Please see the last section of the following page, on "Site Licensing": http://www.mozilla.org/about/legal.html

Reportees search using embedded ldap provider

I am trying to use the embedded ldap server to find a person's reportees by using the inetorgperson attribute "manager". I have imported a number of users using an ldif file.
Here is my search:
Search DN: ou=people,ou=myrealm,DC=myproject
Filter: (&(objectclass=inetOrgPerson)(manager=uid=mgrID,ou=people,ou=myrealm,DC=myproject))
where mgrID is the name of the manager. This search returns no results. I do get results back if I remove the second condition of the filter, i.e. do:
objectclass=inetOrgPerson
Thus, I think the browser is connecting to the ldap server ok. I assume the manager search filter is not working because the manager attribute is not searchable? Is there any way to make it searchable? I couldn't find anything in the documentation about this.

Search filters are composed of attribute match requirements. For example, to construct a search filter to return all the entries in a directory that contain an attribute called uid with one value equal to testuser, the filter would be:
(uid = testuser)

How to use API to access embedded LDAP

how can I access the embedded LDAP through API,such as to query
a user from it. who can give me a example

how can I access the embedded LDAP through API,such as to query
a user from it. who can give me a exampleThere no public API to access LDAP but you can do something
like(programatically)
AuthenticationProviderMBean [] providers =
Admin.getInstance().getActiveDomain().getSecurityConfiguration().findDefault
Realm().getAuthenticationProviders();
for (int i=0; providers != null && i <providers.length; i++)
System.out.println("Providers: " + providers.toString());
if (providers[i] instanceof UserReader)
UserReader reader = (UserReader)providers[i];
try {
} catch (Exception e) {
-utpal

Use of Backup feature in Embedded LDAP

Hi all,
There is a feature in the Admin Console->Security->Embedded LDAP that called Backup.
We can set the Backup Hour and Backup Minute. In fact, what is the meaning of
Backup? Will the server backup automatically during the time that set? Where does
it backup? Will it backup by exporting all information to ldif file?
Thx a lot.

The backup hour triggers WLS to zip up your embedded LDAP data and put it in
a file:
<yourdomain><yourserver>ldap/backup/EmbeddedLDAPBackup.zip
<yourdomain><yourserver>ldap/backup/EmbeddedLDAPBackup.0.zip
<yourdomain><yourserver>ldap/backup/EmbeddedLDAPBackup.1.zip
Etc.
It's not LDIF, it just the straight up LDAP data zipped up. To restore,
unzip it and put it back into the directory
<yourdomain><yourserver>ldap/ldapfiles
See:
http://edocs.bea.com/wls/docs70/secmanage/ldap.html
Mike
"Karen Law" <[email protected]> wrote in message
news:3e4b7232$[email protected]..
>
Hi all,
There is a feature in the Admin Console->Security->Embedded LDAP thatcalled Backup.
We can set the Backup Hour and Backup Minute. In fact, what is the meaningof
Backup? Will the server backup automatically during the time that set?Where does
it backup? Will it backup by exporting all information to ldif file?
Thx a lot.

Issue while starting AdminSerever using wlst commands

Hi, I am facing issue while trying to start the AdminServer and Managed Server via nodemanager using wlst commands. I have installelled WebLogic 11g on windows 2008 R2. Mentioned below are the steps that I followed:
1) In Nodemanager.properties files I set following parameters to true. I did this, so that nodemanager can start the server in case of crash.
CrashRecoveryEnabled=true
StartScriptEnabled=true
2) started nodemanager and then started AdminServer from the command prompt as follows:
nmConnect('weblogic','password','10.23.226.58','5556','IMDomain','E:\Oracle\Middleware\user_projects\domains\IMDomain','ssl')
nmStart('AdminServer')
I dont see any errors but it seems the AdminServer do Not start properly as in the cmd window I don't see any 'started successfully' message - the message remains as *"Starting AdminServer..."*
However in the adminServer logs I see that the status is Running (refer logs at the end) and I can also see it as Running in weblogic console.
I really didnt care if its not giving a success message in cmd window but the problem occurs when I start the managedServer. After starting the managed server in about 10 minutes, there is a stuck thread. (I guess it is 10 mins because Stuck Thread MaxTime value is 600).
If I set StartScriptEnabled=false, and start by directly running the startweblogic.cmd then it works fine.
I am struggling with this for last 1 week, appreciate any help.
LOGS.......
Starting WLS with line:
E:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -Dweblogic.security.SSL.nojce=true -Xverify:none -da -Dplatform.home=E:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dwli.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\integration -Dweblogic.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=E:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;E:\Oracle\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
<Mar 14, 2012 3:16:30 PM CDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Mar 14, 2012 3:16:30 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Mar 14, 2012 3:16:30 PM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.2-b06 from Sun Microsystems Inc.>
<Mar 14, 2012 3:16:31 PM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Mar 14, 2012 3:16:32 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 14, 2012 3:16:32 PM CDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 14, 2012 3:16:32 PM CDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\Oracle\Middleware\user_projects\domains\IMDomain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<Mar 14, 2012 3:16:36 PM CDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 14, 2012 3:16:37 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Mar 14, 2012 3:16:37 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Mar 14, 2012 3:16:39 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
Mar 14, 2012 3:16:39 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.227.211.13:8001 for protocols iiop, t3, ldap, snmp, http.>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "IMDomain" running in Production Mode>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Mar 14, 2012 3:16:40 PM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\PROGRA~1\Java\JDK16~1.0_2\jre\lib\security\cacerts.>
<Mar 14, 2012 3:20:53 PM CDT> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 14:12:27 CST 2002,
               To: Tue Mar 22 15:12:27 CDT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 14, 2012 3:20:53 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 15, 2012 11:41:41 AM CDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "650" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@68a3f7ed", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)
java.io.InputStream.read(InputStream.java:85)
com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)
com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
com.certicom.tls.record.ReadHandler.read(Unknown Source)
com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
java.io.InputStreamReader.read(InputStreamReader.java:167)
java.io.BufferedReader.fill(BufferedReader.java:136)
java.io.BufferedReader.readLine(BufferedReader.java:299)
java.io.BufferedReader.readLine(BufferedReader.java:362)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:289)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:102)
weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:47)
weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<Mar 15, 2012 11:42:41 AM CDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "710" seconds working on the request "weblogic.kernel.WorkManagerWrapper$1@68a3f7ed", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)
java.io.InputStream.read(InputStream.java:85)
com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)
com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
com.certicom.tls.record.ReadHandler.read(Unknown Source)
com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
java.io.InputStreamReader.read(InputStreamReader.java:167)
java.io.BufferedReader.fill(BufferedReader.java:136)
java.io.BufferedReader.readLine(BufferedReader.java:299)
java.io.BufferedReader.readLine(BufferedReader.java:362)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:289)
weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
weblogic.nodemanager.client.NMServerClient.start(NMServerClient.java:102)
weblogic.nodemanager.mbean.StartRequest.start(StartRequest.java:75)
weblogic.nodemanager.mbean.StartRequest.execute(StartRequest.java:47)
weblogic.kernel.WorkManagerWrapper$1.run(WorkManagerWrapper.java:63)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>

Hi chamila,
    I never tried the example. Exception is not clear. Could you please post more stack trace from log files.
Thanks,
Sham

Can't connect to weblogic embedded LDAP from an init block

Hi
I am trying to use weblogic's embedded LDAP directory in an OBIEE RPD initialisation block, using 10g security model in OBIEE 11g. I need the internal user, BISystemUser, to be validated by an init block in the rpd, but I am not able to configure the weblogic LDAP in an init block, as it is done with AD, for example.
I am following the instructions on "Viewing the Contents of the Embedded LDAP Server from an LDAP Browser" section of this document, http://docs.oracle.com/cd/E21764_01/web.1111/e13707/ldap.htm#i1104934 and I am getting: "LDAP bind failure: Can't connect to LDAP server". Weblogic is up and running, I can connect to its console, OBIEE, etc.
I am using this settings on OBIEE:
Hostname: localhost (I've tried using the actual hostname)
Base DN: dc=bifoundation_domain
Bind DN: cn=Admin
Port: 7001
(I've already reset LDAP's Admin password to a known value).
The curious thing is that I can connect to the same LDAP using the same settings with LDAPExplorerTool2 opensource tool.
Does anyone have an idea what else is missing?
Thank you.

i also have this problem..do u have any solution?

URGENT : Add & Retrieve properties from Embedded LDAP in Weblogic 9.2

I am using Embedded LDAP WebLogic 9.2 and i followed the steps mentioned in the URL below.I have nt changed anything except Server URL which points to localhost:7001.
http://e-docs.bea.com/wlp/docs92/users/appendixa.html#wp1055363
Questions:
1)How to add additional attributes to embedded LDAP? (eg email, phone etc).
2)How to read those properties from embedded LDAP using WebLogic Portal API? Any code samples?
Any help is appreaciated.

this problem is due to hard-coded user/pwd in installation scripts. Here are steps
1) open file AIA_HOME/Infrastructure/install/wlscripts/FPWLCommonConfig.xml
2) reach to target CreateStartupClasses
3) there are three java tasks for com.oracle.oems.weblogic.AQJMSPasswordUtility
4) in the task for oraesb, password is hardcoded as 'oraesb' in clear text.
5) this should be password of 'ORAESB' database user.
6) change this password value; and restart the installation.
Regards,
Vaibhav

Settting embedded LDAP password using WLST

Similar Messages

Maybe you are looking for