| Author |
Message
|
| viraj |
 Posted: Thu Oct 03, 2002 3:34 am Post subject: JMS Admin Unable to bind object |
 |
|
Newbie
Joined: 03 Oct 2002
Posts: 9
|
I am trying to configure java objects in ldap using the JMSAdmin tool in SUN SOLARIS. But I am getting the error "Unable to Bind Object".
My JMSAdmin.config file is set up with this following fields
INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
PROVIDER_URL=ldap://localhost:389/ou=mq,o=ibm,c=us
SECURITY_AUTHENTICATION=none
Any Help to solve this problem would be highly regarded.
_________________
Regards
Raj |
|
| Back to top |
|
 |
| middlewareonline |
| Posted: Thu Oct 03, 2002 4:00 pm Post subject: |
|
|
Acolyte
Joined: 09 Jul 2001
Posts: 73
|
Ldap should support Stroring of Java Object. Please see RFC 2713 Schema for Representing Java Objects in an LDAP Directory.
Which LDAP server are you using (version, etc.) ?
Raj
_________________
---------------------------------------------
IBM & SUN (J2EE) Certified Consultants,
http://www.MiddlewareOnline.com
A "SARVAM" Online Portal
http://www.SARVAM.com
--------------------------------------------- |
|
| Back to top |
|
|
| viraj |
| Posted: Fri Oct 04, 2002 12:48 am Post subject: |
|
|
Newbie
Joined: 03 Oct 2002
Posts: 9
|
Hi Raj,
Thanks for the info. I found that my ldap is not supporting the storage of java objects.
We need to ensure that the LDAP schema contains the following information to support java objects.
( 1.3.6.1.4.1.42.2.27.4.2.1
NAME 'javaContainer'
SUP top
MUST cn )
( 1.3.6.1.4.1.42.2.27.4.2.4
NAME 'javaObject'
SUP top
ABSTRACT
MUST javaClassName
MAY javaCodebase )
( 1.3.6.1.4.1.42.2.27.4.2.5
NAME 'javaSerializedObject'
SUP javaObject
AUXILIARY
MUST javaSerializedData
MAY javacodebase )
( 1.3.6.1.4.1.42.2.27.4.2.7
NAME 'javaNamingReference'
SUP javaObject
AUXILIARY
MUST javaclassname
MAY ( javaFactory $ javaReferenceAddress ) )
( 1.3.6.1.4.1.42.2.27.4.1.3
NAME 'javaReferenceAddress'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
( 1.3.6.1.4.1.42.2.27.4.1.4
NAME 'javaFactory'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
( 1.3.6.1.4.1.42.2.27.4.1.6
NAME 'javaCodebase'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
When you have completed the updates, stop and restart the LDAP server
I think this would solve the issue.
Thanks & Regards
-Raj
_________________
Regards
Raj |
|
| Back to top |
|
|
| viraj |
| Posted: Fri Oct 04, 2002 12:13 pm Post subject: |
|
|
Newbie
Joined: 03 Oct 2002
Posts: 9
|
I am getting this "Unable to bind" error even after i configired the ldap to store java objects. What could be the reason.
I am using IPLANET LDAP SERVER V5.1.
_________________
Regards
Raj |
|
| Back to top |
|
|
| middlewareonline |
| Posted: Sat Oct 05, 2002 9:52 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2001
Posts: 73
|
I suggest -
1. Try to test with a sample program that binds a simple object in the LDAP. Your LDAP server comes with a few samples.
DON'T directly try to use JMSAdmin tool. First make sure your configuration is good.
2. Through the GUI ( if there is one for your LDAP) see the object def/attributes are in LDAP.
3. Finally, check the logs after you run JMSadmin tool. Use tracing for JMSAdmin tool. Look for error message.
JMSAdmin -t ( flag for trace)
4. If this does NOT work , I bet you have NOT given access to anonymous user in LDAP. If you are using basic authantication, else to the user you are authenticating.
Raj
_________________
---------------------------------------------
IBM & SUN (J2EE) Certified Consultants,
http://www.MiddlewareOnline.com
A "SARVAM" Online Portal
http://www.SARVAM.com
--------------------------------------------- |
|
| Back to top |
|
|
| viraj |
| Posted: Tue Oct 08, 2002 5:38 am Post subject: |
|
|
Newbie
Joined: 03 Oct 2002
Posts: 9
|
Hi,
I was getting an error called LDAP error 34 which means i am using an invalid DN entry. I rectified my DN entry and now its working fine. I am able to configure my mqobjects in LDAP.
thanks for the help.
_________________
Regards
Raj |
|
| Back to top |
|
|
| middlewareonline |
| Posted: Thu Oct 10, 2002 10:33 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2001
Posts: 73
|
You did not ask for LDAP error 34. Your question was pointing to "Unable to bind object". DN errors generate different trace/log that can be looked into and resolved.
Good that you got it to work.
_________________
---------------------------------------------
IBM & SUN (J2EE) Certified Consultants,
http://www.MiddlewareOnline.com
A "SARVAM" Online Portal
http://www.SARVAM.com
--------------------------------------------- |
|
| Back to top |
|
|
|
|
