× 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.



Thanks, *ALLOBJ works!  I tried giving 777 Authority to KBD file but that
didn't work either.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Matt.Haas@xxxxxxxxxxx
Sent: Wednesday, January 04, 2006 12:36 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: The certificate container *SYSTEM could not be accessed.

Did you try a profile with *ALLOBJ authority? The *SYSTEM certificate
store is probably set up with *PUBLIC *EXCLUDE authority. I don't know
the location of the file(s) but it's probably under either
/QIBM/ProdData or /QIBM/UserData. I'd try looking in the InfoCenter to
see where it's at.

Matt

-----Original Message-----
From: rpg400-l-bounces+matt.haas=thomson.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+matt.haas=thomson.com@xxxxxxxxxxxx] On Behalf
Of Mohammad Tanveer
Sent: Wednesday, January 04, 2006 2:29 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: The certificate container *SYSTEM could not be accessed.

"the certificate container *SYSTEM could not be accessed"

I am getting this message when I am trying to call a java class from
RPGLE
to do a HTTPS post using URL object and standard jar files jcert.jar,
jsse.jar and jnet.jar.

I don't get this error when I use a profile with *SECOFR authority but I
do
get it when I use a *USER profile

Do I have to use *SECOFR for sending https post messages?

Thanks




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.