RE: (GSKit) Access to the key database is not allowed

["Dunn, Steven W" <Steven.Dunn@xxxxxxxxxxxxxxxxxx>]

Thanks for your response Ian, however I'm afraid getting our network security
group to grant *PUBLIC any kind of authority is going to be next to impossible.
The application we're looking to use HTTPAPI with is for C/C authorization and
we have to meet PCI requirements. So, we'll need to be able to limit access to
the key database to a select group which may require setting up a special group
profile exclusively for this application.

Our network security group did indicate they provided *RX rights across the
entire patch. 


Steve Dunn
Sales & Wholesaler Systems
Branded Products Group
Phone: (314) 577-5499
Email: mailto:Steven.Dunn@xxxxxxxxxxxxxxxxxx


-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of ian
Sent: Thursday, May 08, 2008 12:01 PM
To: 'HTTPAPI and FTPAPI Projects'
Subject: RE: (GSKit) Access to the key database is not allowed


Ensure the authorities are granted to all the folders in the chain.
I always grant the additional authorities to *PUBLIC instead of special groups.

If you continue to get the problem, keep increasing the *PUBLIC authority until
it works.
Not forgetting the folders as well in the list.

Regards
 
Ian Patterson


-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Dunn, Steven W
Sent: 08 May 2008 16:14
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Subject: (GSKit) Access to the key database is not allowed



To All,

Using HTTPAPI, I'm trying to validate I can initiate an SSL request from our
system using the 'Example4' function provided, but keep running into
authorization issues with the key database. Using the following instructions
Scott provided a previous user I found in the forum archive,  our server ops and
network security group added a supplemental group profile to my profile with *RX
authority to the following folder path (/QIBM/UserData/ICSS/Cert/Server) and *R
authority to both the DEFAULT.KDB and DEFAULT.RDB files. However I'm still
getting the same error.

I'm running HTTPAPI 1.21 on V5R4.

Any help in resolving this issue would be sincerely appreciated.


 <<Picture (Enhanced Metafile)>> 

Steve Dunn



The information transmitted (including attachments) is covered by the Electronic
Communications Privacy Act,
18 U.S.C. 2510-2521, is intended only for the person(s) or entity/entities to
which it is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other than the
intended recipient(s) is prohibited. If you received this in error, please
contact the sender and delete the material from any computer.


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
The information transmitted (including attachments) is
covered by the Electronic Communications Privacy Act,
18 U.S.C. 2510-2521, is intended only for the person(s) or
entity/entities to which it is addressed and may contain
confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking
of any action in reliance upon, this information by persons
or entities other than the intended recipient(s) is prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------