restful-authentication | used plugin provides a foundation | Authorization library

by technoweenie Ruby Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | restful-authentication Summary

restful-authentication is a Ruby library typically used in Security, Authorization applications. restful-authentication has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This widely-used plugin provides a foundation for securely managing user authentication:. Several features were updated in May, 2008. IMPORTANT: if you upgrade your site, existing user account passwords will stop working unless you use --old-passwords.

Support

Quality

Security

License

Reuse

Support

restful-authentication has a medium active ecosystem.

It has 1575 star(s) with 279 fork(s). There are 16 watchers for this library.

It had no major release in the last 6 months.

There are 23 open issues and 4 have been closed. On average issues are closed in 625 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of restful-authentication is current.

Quality

restful-authentication has 0 bugs and 0 code smells.

Security

restful-authentication has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

restful-authentication code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

restful-authentication is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

restful-authentication releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed restful-authentication and discovered the below as its top functions. This is intended to give you an instant insight into restful-authentication implemented functionality, and help decide if they suit your requirements.

Calculate the checksum

Get all kandi verified functions for this library.

restful-authentication Key Features

No Key Features are available at this moment for restful-authentication.

restful-authentication Examples and Code Snippets

No Code Snippets are available at this moment for restful-authentication.

Community Discussions

Trending Discussions on restful-authentication

Is it wrong to use sessions in Microservices?

QUESTION

Is it wrong to use sessions in Microservices?

Asked 2020-May-19 at 00:24

I have read that, session is against the concept of RESTfulness.

Do sessions really violate RESTfulness?

Session Management in microservices

RESTful Authentication

Since Microservices inevitably use REST, does the same apply here as well? If so, then why do we have Spring session? It even lists 'Spring Session allows providing session ids in headers to work with RESTful APIs' as one of its features.

...

ANSWER

Answered 2020-May-19 at 00:24

Apart from Scaling as an advantage of micro-services, it also provides you with the flexibility to choose polyglot architecture i.e (using the right programming language, framework, database for the right job).

If you use spring sessions(which off-course provides session replication across nodes), internally it uses Redis/gemfire/hazelcast as a replicated session store, but you will have to stick to one programming language & framework for all your services i.e Java & Spring resp.(You can off course write your own implementation in other languages to read from session store, but its re-inventing the wheels) And this will take away Benefit of Polyglot Architecture.

So typically in microservices architecture, you have a token-service(and it should be able to scale individually) implementation to generate tokens(aka sessionIds) which are used for Authentication & Authorization in each service and you should try to avoid storing the session information. It will also help to avoid "Single point of Failure".

Source https://stackoverflow.com/questions/46803321

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install restful-authentication

This is a basic restful authentication generator for rails, taken from acts as authenticated. Currently it requires Rails 1.2.6 or above.
either use git clone git://github.com/technoweenie/restful-authentication.git restful_authentication
or rename the plugin's directory to be restful_authentication after fetching it.
The first parameter specifies the model that gets created in signup (typically a user or account model). A model with migration is created, as well as a basic controller with the create method. You probably want to say "User" here.
The second parameter specifies the session controller name. This is the controller that handles the actual login/logout function on the site. (probably: "Session").
--include-activation: Generates the code for a ActionMailer and its respective Activation Code through email.
--stateful: Builds in support for acts_as_state_machine and generates activation code. (@--stateful@ implies @--include-activation@). Based on the idea at [[http://www.vaporbase.com/postings/stateful_authentication]]. Passing @--skip-migration@ will skip the user migration, and @--skip-routes@ will skip resource generation -- both useful if you've already run this generator. (Needs the "acts_as_state_machine plugin":http://elitists.textdriven.com/svn/plugins/acts_as_state_machine/, but new installs should probably run with @--aasm@ instead.)
--aasm: Works the same as stateful but uses the "updated aasm gem":http://github.com/rubyist/aasm/tree/master
--rspec: Generate RSpec tests and Stories in place of standard rails tests. This requires the "RSpec and Rspec-on-rails plugins":http://rspec.info/ (make sure you "./script/generate rspec" after installing RSpec.) The rspec and story suite are much more thorough than the rails tests, and changes are unlikely to be backported.
--old-passwords: Use the older password scheme (see [[#COMPATIBILITY]], above)
--skip-migration: Don't generate a migration file for this model
--skip-routes: Don't generate a resource line in @config/routes.rb@