RE: [PHP-DB] Authenticating through a php script

2003-01-10 Thread Maureen Roihl
One reason you might be having difficulty is if the remote host does the basic authentication procedure of checking that the username/password is being submitted from a specific host or script (in which case it will see that you're attempting to submit the information from somewhere else and

RE: [PHP-DB] Authenticating through a php script

2003-01-10 Thread Matthew Moldvan
://www.trilogyintl.com/ecommerce/ --- -Original Message- From: Jeremy Peterson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 4:54 PM To: David Smith Cc: [EMAIL PROTECTED] Subject: Re: [PHP-DB] Authenticating through a php script Dave, I am

Re: [PHP-DB] Authenticating through a php script

2003-01-09 Thread David Smith
Jeremy, LDAP authentication happens in two stages: connect and bind. The connect stage is just establishing a connection with the LDAP server (ldap_connect()). No username or password is necesary in this stage. Once your connection is established, you attempt a bind (ldap_bind())to verify a

Re: [PHP-DB] Authenticating through a php script

2003-01-09 Thread Jeremy Peterson
David, I have ldap working, my problem is the second half of my question. The problem script workflow: 1. Authenticate on LDAP (Resolved) 2. Connect to different authenticated site for the user (Not sure where to go now.) My guess was to send the post information to where the form action

Re: [PHP-DB] Authenticating through a php script

2003-01-09 Thread David Smith
I haven't looked over all your code in detail, but the problem you describe seems to be best solved using PHP Sessions. Sessions store data between browser refreshes. You could store whether a user has been authenticated via LDAP, and then on a subsequent page, you can reference that information

Re: [PHP-DB] Authenticating through a php script

2003-01-09 Thread Jeremy Peterson
Dave, I am afraid I am not communicating what I am trying to do. I have multiple databases that my library purchases. FirstSearch, Ebscohost, etc. These company's have there own authentication systems that I have no control over. A lot of them give user names and passwords that can access