|
In the iSeries world using HTTPAPI you connect and the certificate is verified, they send you some redirects, you post your stream file, and that's that. Exit points capture the cookie that they send to you and handle sending it back on subsequent communications. Getting the cookie may be the point of the browser log-in process.
The latest HTTPAPI (which I just released yesterday, and haven't even announced yet) has support for cookies, so you no longer need to muck with exit points... just do:
http_use_cookies(*ON);and HTTPAPI will automatically handle cookies and send them back when appropriate.
I'm not sure why they would require a password with ftp if you were using certificates but it may just be a universal connection point for them but not get used if you've got a certificate.
Because client-side certificates are an optional and infrequently used feature of SSL. I'd say less than 5% of people using SSL use client-side certificates in HTTP. In FTP, that percentage would be much lower.
Without the client-side certificates, how you do communicate user information? The answer is: you type a userid & password.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.