|
Fellow Geeks:The problem with the end-user's Secure Telnet is still ongoing; it's just a bit complicated to get access to test things, and there were other more pressing issues going on.
I had a chance to try it again today, and inexplicably, it got further than it had before. It still isn't happening, and I haven't a clue why.
midrange.com
If I <Select Certificate Store> --> LOCAL CA, I get:
( ) Server/Client Certificate for another iSeries
( ) Object Signing Certificate for another iSeries
( ) User Certificate
none of which seem relevant. If I instead <Select
Certificate Store> --> *SYSTEM, I get:
( ) Server/Client Certificate
and a couple of other options, and if I select that
option, it now offers "Local CA" as an authority choice,
which I'm certain it wasn't offering before, even though
we'd just created the local CA. Taking that option, a
"system certificate creation" form comes up, looking
reasonably familiar even to a V4 jock like myself. I fill
out the form with values that look right to me, but when I
click the submit button, it gives:
"An error occurred while opening the certificate store. Check for file existence and permission."
I can't recall ever seeing anything like this before. Anybody know what could be happening? -- JHHL
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.
