incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ilya musayev (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-1142) Testing LDAP Auth Failed - due to "%" being illegal character in queryfilter
Date Fri, 01 Feb 2013 23:44:12 GMT
ilya musayev created CLOUDSTACK-1142:

             Summary: Testing LDAP Auth Failed - due to "%" being illegal character in queryfilter
                 Key: CLOUDSTACK-1142
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.1.0
         Environment: CentOS 6.3 with CloudStack 4.1 from git on 02/01/2013
            Reporter: ilya musayev
            Priority: Critical

While attempting to test the LdapConfig command, i was unable to succesefully execute the
API command due to 

{ "ldapconfigresponse" : {"errorcode":431,"cserrorcode":9999,"errortext":"queryfilter could
not be decoded, received value (sAMAccountName=%u) which contains illegal characters eg.%"}

This command i'm executing has worked successfully on 4.0, however its broken in latest 4.1
from git. Everything has been encoded properly and i use 8096 to bypass auth mechanism.

Is there a reason why "%" became an illegal character when i ran this command? Please update
the documentation if its no longer required to use "%" as in (sAMAccountName=%u) in query
filter with alternate solution.

If i alter the query filter and make it such that  (sAMAccountName=u)  is no longer there
- it works.

In my attempt to login with user that is on AD LDAP - i get this error:

	at com.sun.jndi.ldap.LdapNamingEnumeration.getNextBatch(
	at com.sun.jndi.ldap.LdapNamingEnumeration.nextAux(
	at com.sun.jndi.ldap.LdapNamingEnumeration.nextImpl(
	at javax.servlet.http.HttpServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.mortbay.jetty.servlet.ServletHolder.handle(
	at org.mortbay.jetty.servlet.ServletHandler.handle(
	at org.mortbay.jetty.servlet.SessionHandler.handle(
	at org.mortbay.jetty.handler.ContextHandler.handle(
	at org.mortbay.jetty.webapp.WebAppContext.handle(
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
	at org.mortbay.jetty.handler.HandlerCollection.handle(
	at org.mortbay.jetty.handler.HandlerWrapper.handle(
	at org.mortbay.jetty.Server.handle(
	at org.mortbay.jetty.HttpConnection.handleRequest(
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(
	at org.mortbay.jetty.HttpParser.parseNext(
	at org.mortbay.jetty.HttpParser.parseAvailable(
	at org.mortbay.jetty.HttpConnection.handle(
	at org.mortbay.thread.QueuedThreadPool$


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message