Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
microsoft.public.exchange.applications
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
javax.naming.AuthenticationNot SupportedException: [LDAP: error code 8 - How to check customer environment before setting env values for JNDI call ?
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
shivaraj  
View profile  
 More options Jun 7 2010, 3:53 am
Newsgroups: microsoft.public.exchange.applications
From: shivaraj <shivaraj.malanna...@gmail.com>
Date: Mon, 7 Jun 2010 00:53:45 -0700 (PDT)
Local: Mon, Jun 7 2010 3:53 am
Subject: javax.naming.AuthenticationNotSupportedE xception: [LDAP: error code 8 - How to check customer environment before setting env values for JNDI call ?
Print | Individual message | Show original | Report this message | Find messages by this author
Hi All,
While connecting to AD via JNDI, I am getting a error like:
javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8
- 00002028: LdapErr: DSID-0C0901FC, comment: The server requires binds
to turn on integrity checking if SSL\TLS are not already active on the
connection, data 0, v1771]

From googling what I came across is, this will be thrown when a
particular flavor of authentication requested is not supported. It may
be specified using specific authentication schemes such those
identified using SASL.

And I also got a hint that, the solution would be to use
env.put("javax.security.sasl.qop","auth-int");

But my query is, I will be running the same LDAP connectivity tool (my
tool) with many customers. So how should I test if they are using
1. Normal LDAP port: 389? or they are using SSL/TSL connection with
different port number ?
2. How to check what security authentication to use ? i.e setting
Context.SECURITY_AUTHENTICATION to "none", "simple", sasl_mech, ?

Is there a sample code which I can run and fetch customer setup
details (about if SSL is enabled or not etc ) before I set my LDAP env
attributes?

Regards,
Shivaraj


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google