Devise Token Auth
proposals
Devise Token Auth | proposals | |
---|---|---|
7 | 15 | |
3,507 | 433 | |
- | 0.2% | |
4.5 | 0.0 | |
12 days ago | over 2 years ago | |
Ruby | ||
Do What The F*ck You Want To Public License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Devise Token Auth
-
Managing redirects to a subdomain after authentication in a React/Rails application using React Router
I have a React single page application using React Router that hooks into a Rails 5 API. The Rails application uses devise_token_auth for authentication. I've successfully created an authentication process that stores the user state in a Redux store on the client side.
-
Is it possible to retrieve the user index with devise ?
Did you send an authorization header with your api call? The error is pretty clear — the request is unauthorized. Devise is expecting session cookies, but your api should use tokens. https://github.com/lynndylanhurley/devise_token_auth
-
Don't make me think, or why I switched to Rails from JavaScript SPAs
I mentioned Identity in my first comment. I've never found it as simple as Devise though - especially in an API only setting.
With Devise there's a third-party Gem you can use called devise_token_auth which deals with everything automatically.
https://github.com/lynndylanhurley/devise_token_auth
-
Working around un-maintained redux-token-auth for redux and react 17 upgrade
redux-token-auth is a great library. What it mainly does is it provides a plug and play auth implementation functionality for ruby on rails based APIs which implement popular devise_token_auth for auth handling.
-
Rails API Authentication with JWT Options
have you looked at https://github.com/waiting-for-dev/devise-jwt or https://github.com/lynndylanhurley/devise_token_auth
-
Best project setup for Rails+React with "remember me" feature
I'd prefer to have a standalone rails API and a react client separately, but that's not mandatory. I discovered a gem called devise_token_auth and it didn't seem to have refresh tokens but it refreshed the tokens on every request anyway so I was pretty happy with it.
-
Devise, The Swiss Army Knife of Rails User Authentication.
As a side note, also check out devise_token_auth here
proposals
-
An intro to TSConfig for JavaScript Developers
target - Specifies the ECMAScript target version for the emitted JavaScript. Defaults to ES3. To ensure maximum compatibility, set this to the lowest version that your code requires to run. ESNext setting allows you to target the latest supported proposed features.
-
Writing RFCs
TC39
-
Pipeline Operator great again!
Current Status: You'd have to check the TC39 proposals repository or the official proposal text for the most recent status. As of my last update, it had not yet reached Stage 4 (final stage) of the TC39 process, which means it wasn't part of the ECMAScript specification yet.
- Set methods proposal reaches stage 3
-
Upcoming ECMAScript features I'm excited about
More proposals can be found on the official GitHub page.
- What to learn in 2022
-
Updates from the 89th TC39 meeting
There were a couple of other proposals that made stage 1 too, can see here.
-
Don't make me think, or why I switched to Rails from JavaScript SPAs
The working group most in charge of JS is ECMA's TC-39 (TC => Technical Committee) [0]. They've been taking a very deliberate, slow path to expanding the "standard" library because they take a very serious view of backwards compatibility on the web. Some proposals were shifted because of conflicts with ancient versions of things like MooTools still out in the wild, for instance. (This was the so-called "Smooshgate" incident [1].)
This may speed up a bit if the Built-In Modules proposal [2] passes, which would add a deliberate `import` URL for standard modules which would give a cleaner expansion point for new standard libraries over adding more global variables or further expanding the base prototypes (Object.prototype, Array.prototype, etc) in ways that increasingly likely have backwards compatibility issues.
TC-39 works all of their proposals in the open on Github [3] and it can be a fascinating process to watch if you are interested in the language's future direction.
[0] https://tc39.es/
[1] https://developers.google.com/web/updates/2018/03/smooshgate
[2] https://github.com/tc39/proposal-built-in-modules
[3] https://github.com/tc39/proposals
- O que são RFCs e como elas funcionam na linguagem PHP
-
Ask HN: Where are the resources for complex architectures for Node.js?
My biggest pointer would be to remember that Java & JavaScript aren't named that way by coincidence. They're two different approaches to a similar problem. Java suffers from Enterprise Development (eg: Enterprise FizzBuzz[0]), JavaScript suffers from Ultimate Accessibility (eg: how many questions on Stack Overflow conflated jQuery and JS?).
> How should exceptions be managed? [...] Has there been a debate about best practice? Where can I find it?
I suggest you handle the errors you can and otherwise let it crash.[1][2] Debates in NodeJS-land have steered towards more monadic/Result-like structures and working synchronous-looking try/catch onto async/await. NodeJS and its various components are open source, you'll have a lot of luck looking around on GH for issues & PRs related to a feature -- same for the language, ECMAScript[3] officially.[4]
Since you mentioned Clojure, have you looked at ClojureScript?[5] That may be a good entry to JS authors & articles you'd enjoy.
> I have the impression that NodeJS is a bit more magical than the JVM [...] Is that correct? Where are good resources on this subject?
As other replies have mentioned, you're really talking about V8[6] for the "JSVM" executing that code. A thing I've seen throw some people for a loop is how minimalist the specification actually is.[7] The magic in NodeJS is certainly from V8 and the rate of optimizations there but also libuv,[8] what actually powers the infamous event loop.
Hope that helps!
[0]: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
[1]: Borrowing from Erlang, see Making reliable distributed systems in the presence of software errors, Joe Armstrong, page 104 "Error Handling Philosophy" https://erlang.org/download/armstrong_thesis_2003.pdf
[2]: _Most_ kinds of errors will cause the process to crash if you don't handle them, https://nodejs.org/dist/latest-v16.x/docs/api/errors.html . Promise rejections don't (yet) though it emits an error, and callback-based APIs will always consist of an [error, data] tuple for the arguments
[3]: https://github.com/tc39/proposals
[4]: Because Oracle owns the trademark, of course: http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=
[5]: https://clojurescript.org/
[6]: https://v8.dev/docs
[7]: "ECMAScript as defined here is not intended to be computationally self-sufficient; indeed, there are no provisions in this specification for input of external data or output of computed results. Instead, it is expected that the computational environment of an ECMAScript program will provide not only the objects and other facilities described in this specification but also certain environment-specific objects, whose description and behaviour are beyond the scope of this specification except to indicate that they may provide certain properties that can be accessed and certain functions that can be called from an ECMAScript program." https://tc39.es/ecma262/#sec-overview
[8]: https://github.com/libuv/libuv
What are some alternatives?
JWT - A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.
DIPs - D Improvement Proposals
Devise - Flexible authentication solution for Rails with Warden.
peps - Python Enhancement Proposals
Doorkeeper - Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape.
proposal-set-methods - Proposal for new Set methods in JS
devise-jwt - JWT token authentication with devise and rails
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
Knock - Seamless JWT authentication for Rails API
temporal-polyfill - Polyfill for Temporal (under construction)
OmniAuth - OmniAuth is a flexible authentication system utilizing Rack middleware.
proposal-change-array-by-copy - Provides additional methods on Array.prototype and TypedArray.prototype to enable changes on the array by returning a new copy of it with the change.