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



Rob,

This isn't for serving certificates on a server or web application, it's a
client making a request to a server from the IBM i.

The user needs to have at least *R authority (and *RX to the directory) so
it can read the SSL keyring files so it can hopefully find the proper
Certificate Authorities (CAs) so it "trusts" the SSL certificate used by
the server.

Not sure why it comes shipped with *PUBLIC exclude. I'm sure there's a
good reason. ;)

Brad
www.bvstools.com

On Fri, May 20, 2016 at 1:32 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Dumb question of the day. Does the AF entry in the audit journal tell you
the name of the user? I would figure for a web job it would be some IBM
type user profile serving up the certificates. Just add them?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: "MIDRANGE-L (midrange-l@xxxxxxxxxxxx)" <midrange-l@xxxxxxxxxxxx>
Date: 05/20/2016 02:02 PM
Subject: /QIBM/UserData/ICSS/Cert/Server & HTTPS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I'm doing an HTTPS webservice call out of RPG. It's giving me an
authority failure on this dir: /QIBM/UserData/ICSS/Cert/Server. The
default authority for that dir is:
*PUBLIC *EXCLUDE
QSYS *RWX X X X X

I'm reluctant to just blindly grant authority. Does anyone have any
experience with this?

Thanks


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.