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"

Reply via email to