|
thanks Jack,
so i'm proceeding with my original approach when I asked my question
earlier...
From the IBM DCM, I can produce a server side certificate and from my
understanding also a pub/prv key pair.
The trick is extracting and separating the cert/key.
I'm following the link below.
With the cert and key file in hand, i can test via postman/ARC and then
hand those 2 items to any 3rd party outside my intranet to make api calls.
if anyone is familiar with the below link/process, assistance would be
appreciated if you can.
My current version of the key store is not the same as in the link tutorial
so that is throwing me off.
https://www.ibm.com/support/pages/how-export-certificate-digital-certificate-manager-dcm-key-store-ibm-key-management-ikeyman
jay
On Tue, Apr 28, 2020 at 2:34 PM Jack Woehr <
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
On Tue, Apr 28, 2020 at 11:28 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>client
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
is handed a self-signed cert.storing
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
certs for IBM i apps to present when they themselves are a client to somehandled
server somewhere.
Authorization by means of client certs incoming to IBM i has to be
by the app itself. Perhaps WAS has some support for that, etc.list
--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.