×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, Apr 28, 2020 at 11:28 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:
Thanks Jack but the certificate extraction method you walked me through
earlier, is that not a level of security authentication?
Not really. It allows a client to believe your server.
"Real" https requires the cert that your server presents to be
authenticated thru a chain of Certificate Authorities (CAs).
You have a self-signed cert, so you have to provide it through another
channel (e.g., email) to your clients so they can add it to their trust
store manually, since it can't be verified through well-know CAs.
Anyone else would just have to trust the cert. Their session would be
encrypted, sure, but with whom? No way to know automatically when a client
is handed a self-signed cert.
As for THE CLIENT proving itself to THE SERVER (authorization) that's a
whole 'nother ball of wax.
There are such things as client certs. DCIM supports them as far as storing
certs for IBM i apps to present when they themselves are a client to some
server somewhere.
Authorization by means of client certs incoming to IBM i has to be handled
by the app itself. Perhaps WAS has some support for that, etc.
midrange.com
