Re: put in safety my Rest Web Services

I can vouch for Jared Hanson's passport stuff as I have used it myself in a Sails app. My only complaint would be a lack of supporting documentation and examples, so it took me a while to fathom it all out....probably me being a node newb more than anything else.

Sent from my iPad

On 20 Aug 2015, at 15:04, Aaron Bartell <aaronbartell@xxxxxxxxx> wrote:

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.

Here's a start. . . In reality, there are many many options. I generally
stick with the most popular options since popularity is one aspect of
lessening risk.

Ruby:
- Authentication:
https://www.ruby-toolbox.com/search?utf8=%E2%9C%93&q=authentication
- Authorization:
https://www.ruby-toolbox.com/search?utf8=%E2%9C%93&q=authorization
- Access/Encryption: Devise - https://github.com/plataformatec/devise

Node.js
- https://github.com/jaredhanson/passport
etc....


Aaron Bartell

On Thu, Aug 20, 2015 at 7:36 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

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