Re: Authentication problem in Remedy LDAP for passwords with special characters. -- RESOLVED.
Thank you all for pointing me in the right direction, it all seems very
trivial now.
The special characters were breaking the URL since the parameters to the
ViewFormServlet were not being encoded (the servlet expects encoded data).
The ARServerUser API of course does not accept the encoded parameters, so we
ended up passing plain data to the API and encoded data to the
ViewFormServlet.
Also,thank you Axton for suggesting that I use the forward instead of
re-direct, I have modified the code per your suggestion.
Thanks again.
Prasan.
On 8/13/07, Hugo Visser <[EMAIL PROTECTED]> wrote:
>
> ** 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 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:* arslist@ARSLIST.ORG
> > > *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:arslist@ARSLIST.ORG
> > > > > ] *On Behalf Of *Prasan Katti
> > > > > *Sent:* Thursday, August 09, 2007 2:51 PM
> > > > > *To:* arslist@ARSLIST.ORG
> > > > > *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
> >
Re: Authentication problem in Remedy LDAP for passwords with special characters.
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 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:* arslist@ARSLIST.ORG
> > *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:arslist@ARSLIST.ORG
> > > > ] *On Behalf Of *Prasan Katti
> > > > *Sent:* Thursday, August 09, 2007 2:51 PM
> > > > *To:* arslist@ARSLIST.ORG
> > > > *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"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
Well, that's kind of a nasty way of passing auth info around. Certain
characters, like pound (#) will break your url if they are not encoded
properly.
I say nasty because you are sending sensitive information (username
and password) over the wire unprotected. You may want to look into
using a forward instead of a redirect.
Axton Grams
On 8/9/07, Prasan Katti <[EMAIL PROTECTED]> wrote:
> **
> 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:arslist@ARSLIST.ORG ] On Behalf Of Prasan Katti
> > > Sent: Thursday, August 09, 2007 2:51 PM
> > > To: arslist@ARSLIST.ORG
> > > 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___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
I seem to recall when some version of Java had problems passing special characters. I don't recall which versions though. HTH somewhat. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Prasan Katti Sent: Thursday, August 09, 2007 2:06 PM To: arslist@ARSLIST.ORG Subject: Re: Authentication problem in Remedy LDAP for passwords with special characters. ** No..all the data is being posted as plain text. Should I encode the password?? Also, I noticed that the Remedy login.jsp has enctype="x-www-form-encoded" in the 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: ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
No..all the data is being posted as plain text. Should I encode the
password??
Also, I noticed that the Remedy login.jsp has enctype="x-www-form-encoded"
in the 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:* arslist@ARSLIST.ORG
> *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:arslist@ARSLIST.ORG
> > > ] *On Behalf Of *Prasan Katti
> > > *Sent:* Thursday, August 09, 2007 2:51 PM
> > > *To:* arslist@ARSLIST.ORG
> > > *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___
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
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: arslist@ARSLIST.ORG
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+"&usern
ame="+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:arslist@ARSLIST.ORG ] On Behalf Of Prasan Katti
Sent: Thursday, August 09, 2007 2:51 PM
To: arslist@ARSLIST.ORG
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___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
We are on Windows 2000/2003 servers / SQL Server 2000/2005 / IIS5/6/Tomcat 5.5 but are also authenticating to eDir on Linux, and have been since 2003 with 5.1.2 production systems and every ARS version since then in test/development. We even got SSL working (no fun at all with certificates - easy with sTunnel). I have not seen problems with special characters (certainly not # or *) and our password reset interface to eDir requires at least one special character to be used. The only special character to AVOID is the semi-colon, since the ODBC driver that mid-tier and the User Tool use for crystal reporting will consider it to be the end of the password and you will be unable to authenticate over ODBC. Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://remedy.unt.edu/helpdesk/ _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Prasan Katti Sent: Thursday, August 09, 2007 3:02 PM To: arslist@ARSLIST.ORG Subject: Re: Authentication problem in Remedy LDAP for passwords with special characters. ** 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:arslist@ARSLIST.ORG ] On Behalf Of Prasan Katti Sent: Thursday, August 09, 2007 2:51 PM To: arslist@ARSLIST.ORG 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___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
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.jspin 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:arslist@ARSLIST.ORG
> > ] *On Behalf Of *Prasan Katti
> > *Sent:* Thursday, August 09, 2007 2:51 PM
> > *To:* arslist@ARSLIST.ORG
> > *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___
>
>
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
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:* arslist@ARSLIST.ORG > *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___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
I've had no problem with special characters on Windows platforms with
Active Directory as the LDAP server, either via the User Tool or the Mid
Tier. My first guess would be that it may be Remedy's plugin to Novell
being the problem.
Shawn Pierson
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Prasan Katti
Sent: Thursday, August 09, 2007 2:51 PM
To: arslist@ARSLIST.ORG
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___
Private and confidential as detailed http://www.sug.com/disclaimers/default.htm#Mail";>here. If you cannot
access hyperlink, please e-mail sender.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
Re: Authentication problem in Remedy LDAP for passwords with special characters.
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: arslist@ARSLIST.ORG 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. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
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. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
