The only stash file I could find was one for WEBQRY.
I copied over the DEFAULT.KDB and DEFAULT.RDB files, fixed up the file ownership and permissions on the parent folder and everything seems to be working fine with all of our banking applications that use certs.
I'm going to be setting SSL on some of the standard ports shortly as well, so I'll see if copying the file causes any issues from more of the IBM side versus our third party applications. If I have any issues, I'll see if the restore does a better job.
Core Processing Administrator/Analyst
Washington Trust Bank
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Thursday, June 05, 2014 09:32
To: Midrange Systems Technical Discussion
Subject: Re: Any Problems Foreseen Copying Certificate Store from One i to Another i?
Stash file is critical and I don't recall that you can simply copy the file either. It is restored with:
RSTUSRPRF USRPRF(*NONE) SECDTA(*DCM)
- Larry "DrFranken" Bolhuis
On 6/4/2014 1:31 PM, Chris Bipes wrote:
Make your you also get the .sth (stash) file as it holds you encrypted password to access the certificate store. I personally tried and failed. (I missed the stash file) So good luck. If it does not work, you just delete the IFS file and start from scratch.
Director of Information Services
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Wednesday, June 04, 2014 9:43 AM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: Any Problems Foreseen Copying Certicate Store from One i to Another i?
We're setting up a test partition and have a bunch of certificates in the system certificate store on our production partition that also need to be on our test partition. Are there any negatives to copying the store from the production partition to the test partition? Test partition store is brand new so I'd rather be lazy and not export all the certs from production and import them on test if there are no issues with just copying it over.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
This electronic mail message and any attachments may contain confidential or privileged
information and is intended for use solely by the above-referenced recipient. Any review,
copying, printing, disclosure, distribution, or other use by any other person or entity is
strictly prohibited under applicable law. If you are not the named recipient, or believe
you have received this message in error, please immediately notify the sender by replying
to this message and delete the copy you received. =====================================================================================================