Ldap Error Code 48 Inappropriate Authentication
Contents |
Server-Side Result Codes Various LDAP specifications define a number of common result codes that may be included in responses to clients. These result codes include (but are not necessarily limited to): 0: Success This indicates that the operation completed successfully. It may ldap error code 16 - no such attribute be returned in response to an add, bind, delete, extended, modify, modify DN, or search operations.
Ldap Error Code 49 - Invalid Credentials
Compare operations will not return a success result. If a compare operation does not encounter an error during processing, then the server should return a result of either "compare true" or "compare false", based on whether the target entry had the specified attribute value. 1: Operations Error This is intended to indicate that the client has requested an operation at an inappropriate time or in an incorrect order. For example, it may be used if a client sends a non-bind request in the middle of a multi-stage bind operation. Note that some directory servers use this as a generic "server error" type result. This is not the intended use for this result code (the "other" result is a better choice for this), but clients may need to be aware of this possibility. 2: Protocol Error This generally indicates that the client request was improperly formatted in some way. For a bind operation, it may indicate that the client attempted to use an unsupported LDAP protocol version. For an extended operation, it may indicate that the server does not support the extended request type. Note that this result code can only be used if the server is able to at least partially decode the request in order to determine the message ID and operation type, since the server needs that information in order to craft an appropriate response. 3: Time Limit Exceeded This indicates that a search operation took longer to complete than allowed by the maximum time limit for that operation. This may be the time limit specified by the client in the search request, or it may be a time limit imposed by the server. 4: Size Limit Exceeded This indicates that a search operation would have returned more entries than were allowed for that operation. This may be the size limit specified by the client in the search request, or it may be a size limit imposed by the server. Note that the server may return a portion of the matching entries before this result. 5: Compare False This indicates that a compare operation was processed successfully but that the target entry did not match the provided attribute value assertion. 6: Compare True This indicates that a compare operation was processed successfully and that the target entry matched the provided attribute value assertion. 7: Authentication Method No
JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. All Places > Support > Openfire Support > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is archived 3 Replies Latest reply on Mar 7, 2006 8:55 AM by slushpupie Can not authenticate users from an openldap server guyj Mar 6, 2006 5:25 AM Hi All,I have installed wildfire 2.5 and now I’m trying to connect https://www.ldap.com/ldap-result-code-reference to an open ldap server. Ldap configurations are as follows. but when I’m trying to connect it gives me errors. Debug log shows following errors.Trying to find a user''s DN based on their username. uid: dummy1x, Base DN: ou=People,dc=xxx,dc=net...Creating a DirContext in LdapManager.getContext()...Created hashtable with context values, attempting to create context...... context created successfully, returning.Starting LDAP search...... https://community.igniterealtime.org/thread/18429 search finishedIn LdapManager.checkAuthentication(userDN, password), userDN is: uid=dummy1x...Created context values, attempting to create context...Caught a naming exception when creating InitialContextjavax.naming.AuthenticationNotSupportedException: LDAP: error code 48 - Inappropriate Authentication 6390Views Tags: none (add) This content has been marked as final. Show 3 replies Re: Can not authenticate users from an openldap server slushpupie Mar 6, 2006 6:17 AM (in response to guyj) What sort of ldap server configuration do you have? Wildfire will try to do a bind to the ldap server with the user signing in, and the password supplied. It should be the rough equivalent to this command:ldapwhoami -x -D "uid=dummy1x,ou=People,dc=xxx,dc=net" -W -h 192.168.11.215 If that command fails, you need to change your openldap configs a bit to make it work. Like Show 0 Likes(0) Actions Re: Can not authenticate users from an openldap server guyj Mar 6, 2006 7:00 PM (in response to slushpupie) Thanks for the quick reply. Can you tell me what are the configurations should I look into because I’m new to LDAP and wildfire. I tried the
and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor. Announcement Announcement Module http://forum.spring.io/forum/spring-projects/security/56679-ldap-problem Collapse No announcement yet. LDAP problem Page Title Module Move Remove Collapse This topic is closedX X Conversation Detail Module Collapse Posts Latest Activity Search Forums Page of https://groups.google.com/d/topic/jasig-cas-user/Qqq7mnl1i1Y 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: Clear All new ldap error posts yxan Junior Member Join Date: Sep 2007 Posts: 3 #1 LDAP problem Dec 11th, 2008, 06:10 PM when i direct this to my company ldap i get: [LDAP: error code 48 - Inappropriate Authentication]; nested exception is javax .naming.AuthenticationNotSupportedException: [LDAP: error code 48 - Inappropriat e Authentication] I feel like I need to somehow ldap error code add a password encoder sha, but not certain where I can do that? here is my config HTML Code:
inHidden fieldsSearch for groups or messages