That makes perfect sense - authentication in the AR System has ALWAYS
been case sensitive for both Login Name and Password, no matter where it
was going to validate the password (User form, LDAP, AD, etc.).

Christopher Strauss, Ph.D.
Remedy Database Administrator
University of North Texas Computing Center
http://itsm.unt.edu/ 


  _____  

        From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of White, Ed
        Sent: Wednesday, November 07, 2007 12:07 PM
        To: [email protected]
        Subject: Re: Case Sensitive User IDs?
        
        
        ** 
         This happens all the time to our users.  We have the cross
reference and authenicate unregistered.  The must type their name
exactly as it is in the user form or they will on receive a Read License
and Public Permissions.
         
        In this case they are not guest users but unregistered users.
         

        Ed White 
        Senior Systems Consultant 
        The Ohio State University Medical Center 
        640 Ackerman Road 
        PO Box 183111 
        Columbus, Ohio 43218-3111 
        (614) 293-2089 (phone) 
        [EMAIL PROTECTED] 

         

  _____  

        From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Sokol, Brian
        Sent: Wednesday, November 07, 2007 1:01 PM
        To: [email protected]
        Subject: Re: Case Sensitive User IDs?
        
        
        ** 
        According to the user log they are getting a Read license. We
have plenty of floating licenses available. The users in question all
have at least App-Support permissions and should be given a floating
write license.

  _____  

        From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Thad K Esser
        Sent: Wednesday, November 07, 2007 12:55 PM
        To: [email protected]
        Subject: Re: Case Sensitive User IDs?
        
        
        ** 
        You say they get a "read" license.  Could you be running out of
floats and the case sensitivity is just a coincidence? 
        
        When this situation does happen, what permissions does the user
end up with?  Is it just public or does it match the user record
(hopefully the user record has permissions other than public)?  That
would tell you a little bit about what is happening during login. 
        
        Thad Esser
        Remedy Developer
        "Argue for your limitations, and sure enough, they're yours."--
Richard Bach 
        
        
        
"Sokol, Brian" <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)"
<[email protected]> 

11/07/2007 09:40 AM 
Please respond to
[email protected]


To
[email protected] 
cc
Subject
Re: Case Sensitive User IDs?    

                




        No we do not allow guest users. 
        
        -----Original Message-----
        From: Action Request System discussion list(ARSList)
        [mailto:[EMAIL PROTECTED] On Behalf Of Joseph Kubasek
        Sent: Wednesday, November 07, 2007 12:28 PM
        To: [email protected]
        Subject: Re: Case Sensitive User IDs?
        
        Do you allow guests? Is it possible the the users are getting
logged in
        as a guest. For example:
        Network account: JoeUser
        remedy account: joeuser
        User types:        JoeUser
        
        In this case, if you allow unauthenticated guests, then remedy
would log
        the user in as the guest user JoeUser instead of the the defined
user
        joeuser.
        
        Joe Kubasek
        
        On Nov 7, 2007 9:46 AM, Sokol, Brian <[EMAIL PROTECTED]>
wrote:
        > **
        >
        >
        > Can someone clear this up for me as it seems to come up a
couple times
        
        > per year. We are using network authentication (not area ldap).
Both 
        > cross reference blank passwords and authenticate unregistered
users
        are checked.
        > All our staff have blank passwords in the User form. Every now
and 
        > then a user only gets a read license. The problem seems to
occur when 
        > the user enters an ID in Remedy that does not match the case 
        > sensitivity of their network account (network account is
JoeUser, 
        > Remedy account is joeuser). I am using the special field 
        > Authentication Login Name (field ID 117) which matches exactly
their
        network ID.
        >
        > Any ideas why this happens? Is the Remedy user ID case
sensitive? 
        > Shouldn't field ID 117 fix any problem? Is this another old
bug 
        > reintroduced by my upgrade to 7.1?
        >
        > One other question. In the user log I am seeing Impersonated
by 
        > MidTier Service when some users login?
        >
        > ARS/MidTier 7.1 on IIS.
        >
        > Thanks
        >
        > Brian Sokol
        > Manager, Desktop Services
        > Scholastic Inc.
        > 557 Broadway
        > NY, NY 10012
        > (212) 343-6494
        > http://www.Scholastic.com
__20060125_______________________This 
        > posting was submitted with HTML in it___
        
        
________________________________________________________________________
        _______
        UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum
        Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
        
        
________________________________________________________________________
_______
        UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
        Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are"
        
        
        

        ***IMPORTANT NOTICE: This communication, including any
attachment, contains information that may be confidential or privileged,
and is intended solely for the entity or individual to whom it is
addressed. If you are not the intended recipient, you should delete this
message and are hereby notified that any disclosure, copying, or
distribution of this message is strictly prohibited. Nothing in this
email, including any attachment, is intended to be a legally binding
signature.***
        

        __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
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to