Re: put in safety my Rest Web Services

Beat me to it, Kevin. I was going to express the same thing.

OAuth is complicated if you don't have the base toolset to communicate
(such as HTTP API or our GETURI application).

Then the next most complicated part is the base of retrieving and storing
the tokens and expiration dates. Pretty much every call to a web service
looks like:

1. Is token expired? If so, get a new one
2. Make API call

If you need to do the OAuth on both ends it can get a little burdensome.
But not impossible.

Brad
www.bvstools.com

On Thu, Aug 20, 2015 at 7:57 AM, Kevin Turner <
kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:

Nathan

An interesting assertion that oauth and oauth2 are good for web
applications but not web services. What leads you to such a conclusion?
The entire Twitter API, Facebook API (graph) and Google API are all web
services, and all use either oauth or oauth2, so their web developers don't
concur with that assertion.

I happen to agree with Brad when he cites these options as the best
available. I just happen to think they are a little complicated to
implement in a purely RPG world, so a different (simplified) option might
be preferable - or a switch to something more geared up for the job.

My five-penneth FWIW

Rgds
Kevin


Sent from my iPad

On 20 Aug 2015, at 14:36, Nathan Andelin <nandelin@xxxxxxxxx> w

My question is how could protect the Web Service's call.

There are 4 rules to security:

1. Authentication.
2. Authorization.
3. Access.
4. Encryption.

Web applications and services typically use HTTPS for "transport
encryption". Private web services may supplement with an additional keyed
based encryption algorithm.

"Authentication" requires issuing "credentials" (User ID and Password,
generally) and a challenge for valid credentials via an "entry point"

URL.

"Authorization" requires granting "authority" to users to various
"services" which is generally managed in a database.
"Access" is the process of exposing private URLs which may be dynamically
generated and assigned to "sessions" based on "authentication" and
"authority", where sessions may expire.
Dynamically generated private URLs may be further encrypted by issuing a
private key to a user (ie "abc123" may be the encryption key for user
"xyz").

Regarding the discussion about "single sign-on" (oAuth, etc.), that seems
only appropriate for web applications (browser user interfaces), but
inappropriate for web services (private user interfaces).

Regarding the discussion about tooling available in other language
environments, I'm not aware of any "tooling" which adequately implements
all of the rules indicated above.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing

list

To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


___________________________________________
This email has been scanned by iomartcloud.
http://www.iomartcloud.com/

________________________________

NOTICE: The information in this electronic mail transmission is intended
by CoralTree Systems Ltd for the use of the named individuals or entity to
which it is directed and may contain information that is privileged or
otherwise confidential. If you have received this electronic mail
transmission in error, please delete it from your system without copying or
forwarding it, and notify the sender of the error by reply email or by
telephone, so that the sender's address records can be corrected.




--------------------------------------------------------------------------------


CoralTree Systems Limited
Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton
Hampshire
SO15 2EA
VAT Registration Number 834 1020 74.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.