Basically the API is behind a firewall. No external users can access.
So if you want all INTERNAL users to access, then you are fine.

If there is sensitive information being passed from/to API, probably good
idea to go over a secure (SSL) connection.

By end of 2020, you will have additional security features, highlighted
by assigning users to roles and protecting APIs via roles, so that users
with required roles will only be authorized to the API.

"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 12/02/2020 07:18:13

From: Robert Rogerson <rogersonra@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
Date: 12/02/2020 07:18 AM
Subject: [EXTERNAL] [WEB400] HTTP and Web server configuration and
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

I was able to create an HTTP and web services servers from the wizard. I
then created an api. I was able to test it with Postman and everything
checked out.

The next thing I'm unsure of is security.

I created a new user with *USER authority and no special authority I
changed the initial menu to signoff.
I redeployed the web service speciying this user profile on User ID for
this service.
I retested with Postman and it still works.

I ended my vpn. The api now timed out in Postman.

So my question is, if the api is only ever called from behind the vpn is
there still a big hole I'm missing?
Is SSL required if behind a vpn?

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 by 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.