Fred is right here, you are building a new URL you should escape the special characters in the url. Anything else does not count as a valid url and might work (on IIS for example) or might not work (on anything else :P)
URLEncoder would be the class you'd use for this in Java. Hugo On 8/9/07, Prasan Katti <[EMAIL PROTECTED]> wrote: > > ** No..all the data is being posted as plain text. Should I encode the > password?? > Also, I noticed that the Remedy login.jsphas enctype="x-www-form-encoded" in > the <form> tag...would this make a > difference? > > Thanks, > Prasan. > > > On 8/9/07, Grooms, Frederick W <[EMAIL PROTECTED]> wrote: > > > > ** Are you URL encoding the special characters inside the password > > variable? > > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto:[EMAIL > > PROTECTED] > > *On Behalf Of *Prasan Katti > > *Sent:* Thursday, August 09, 2007 3:30 PM > > *To:* [email protected] > > *Subject:* Re: Authentication problem in Remedy LDAP for passwords with > > special characters. > > > > > > ** Additionally, we have a custom login.jsp page and are basically using > > the Java api to authenticate users as shown below: > > > > > > ARServerUser ctx=new ARServerUser(username,password,locale,server,port); > > try > > { > > ctx.login(); > > auth= true; > > } > > catch(Exception e) > > { > > auth = false; > > errMsg="Please check the username/password"; > > } > > finally > > { > > ctx.clear(); > > } > > if(auth) > > { > > String > > url="/arsys/servlet/ViewFormServlet?form=APPFORM&server="+server+"&username="+username+"&pwd="+password+"&mode=create"; > > > > response.sendRedirect(url); > > } > > > > Also, just found out that the passwords work fine with the default > > login.jsp in the mid-tier. So could this problem have to do something > > with the above code using Java api or the server JVM?? > > > > Thanks, > > Prasan. > > > > > > On 8/9/07, Prasan Katti <[EMAIL PROTECTED] > wrote: > > > > > > The ARS server is running on Solaris 9 but the LDAP server is on Suse > > > Linux. > > > > > > On 8/9/07, Grooms, Frederick W <[EMAIL PROTECTED] > wrote: > > > > > > > > ** What OS is the ARS Server running on? > > > > > > > > ------------------------------ > > > > *From:* Action Request System discussion list(ARSList) > > > > [mailto:[email protected] > > > > ] *On Behalf Of *Prasan Katti > > > > *Sent:* Thursday, August 09, 2007 2:51 PM > > > > *To:* [email protected] > > > > *Subject:* Authentication problem in Remedy LDAP for passwords with > > > > special characters. > > > > > > > > > > > > Hello Listers, > > > > > > > > We have recently started using the AREA LDAP plugin to authenticate > > > > our remedy users with the LDAP server. > > > > We are cross referencing blank passwords and are having problems > > > > authenticating users whose password contain special characters (#,@,& > > > > etc). > > > > We are able to authenticate these users against the LDAP server > > > > using a different client (like LDAP Browser), so the problem could be > > > > with > > > > the Remedy plugin. > > > > The LDAP server is basically the Novell eDirectory used within the > > > > organization. > > > > If anybody here has faced similar problems before or if I am missing > > > > something obvious (server settings?), please let me know.' > > > > > > > > The server environment is ARS 6.3 patch 21, Tomcat 2.0.51 running on > > > > Oracle 9i database. > > > > > > > > Thanks in advance, > > > > Prasan. > > > > > > > > > > > > __20060125_______________________This posting was submitted with > > > > HTML in it___ > > > > > > > > > > > __20060125_______________________This posting was submitted with HTML in > > it___ > > __20060125_______________________This posting was submitted with HTML in > > it___ > > > > __20060125_______________________This posting was submitted with HTML in > it___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
