devise-jwt 0.5.0 → 0.5.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 7d9d15287c66562066c4c4a729506396e7ec4007
4
- data.tar.gz: 1043788671b10218a3bc7c778f10a2f2c258ee84
3
+ metadata.gz: 40863b765f36af4c045c694d74e8b8a40c81f202
4
+ data.tar.gz: 3c96394c50b8e6a393c9ebee373be62bfde8157e
5
5
  SHA512:
6
- metadata.gz: 1fb0e64bff0707c6a476868f5b1ed9fe967472e0fa385dac3e7c74b8f54433a98d57b1e16b057e59d566721ab91444aed1ec5ece13e309867c43da5bfe5554c4
7
- data.tar.gz: d2cb740987f7c7321a16a38def56fb7e31e90cc4b17f3cdb37ae65f38ac308b64619d52e4ac929f5fbab0ccb18e264837805a98342a9160710df806413b5e9f9
6
+ metadata.gz: 52f0104471824acecb959fe8335165b1187606e1727e9ad5423db51225a6bbaf1264b109346042018a122978cc3ff75a2a64910a05aa37b1d294a2361657cb68
7
+ data.tar.gz: f36d8acd62aa6f70c4a661d6df51bb6486aefa600246f69e8781ca6358b86395318faa984da70375528ea632919666b1347e8fc5987d97bd3e48b4551eb2e82d
@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
4
4
  The format is based on [Keep a Changelog](http://keepachangelog.com/)
5
5
  and this project adheres to [Semantic Versioning](http://semver.org/).
6
6
 
7
+ ## [0.5.1] - 2017-12-11
8
+ ### Added
9
+ - Update `warden-jwt_auth` dependency to ensure JWT scopes are not fetched from
10
+ session
11
+
7
12
  ## [0.5.0] - 2017-12-11
8
13
  ### Added
9
14
  - Added whitelist strategy
data/README.md CHANGED
@@ -26,7 +26,7 @@ You can read about which security concerns this library takes into account and a
26
26
  Add this line to your application's Gemfile:
27
27
 
28
28
  ```ruby
29
- gem 'devise-jwt', '~> 0.5.0'
29
+ gem 'devise-jwt', '~> 0.5.1'
30
30
  ```
31
31
 
32
32
  And then execute:
@@ -39,6 +39,8 @@ Or install it yourself as:
39
39
 
40
40
  ## Usage
41
41
 
42
+ First you need to configure devise to work in an API application. You can follow the instructions in this project wiki page [Configuring devise for APIs](https://github.com/waiting-for-dev/devise-jwt/wiki/Configuring-devise-for-APIs) (you are more than welcome to improve them).
43
+
42
44
  ### Secret key configuration
43
45
 
44
46
  First of all, you have to configure the secret key that will be used to sign generated tokens. You can do it in the devise initializer:
@@ -22,7 +22,7 @@ Gem::Specification.new do |spec|
22
22
  spec.require_paths = ["lib"]
23
23
 
24
24
  spec.add_dependency 'devise', '~> 4.0'
25
- spec.add_dependency 'warden-jwt_auth', '~> 0.3.0'
25
+ spec.add_dependency 'warden-jwt_auth', '~> 0.3.1'
26
26
 
27
27
  spec.add_development_dependency "bundler", "~> 1.12"
28
28
  spec.add_development_dependency "rake", "~> 10.0"
@@ -2,6 +2,6 @@
2
2
 
3
3
  module Devise
4
4
  module JWT
5
- VERSION = '0.5.0'
5
+ VERSION = '0.5.1'
6
6
  end
7
7
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: devise-jwt
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.0
4
+ version: 0.5.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Marc Busqué
@@ -30,14 +30,14 @@ dependencies:
30
30
  requirements:
31
31
  - - "~>"
32
32
  - !ruby/object:Gem::Version
33
- version: 0.3.0
33
+ version: 0.3.1
34
34
  type: :runtime
35
35
  prerelease: false
36
36
  version_requirements: !ruby/object:Gem::Requirement
37
37
  requirements:
38
38
  - - "~>"
39
39
  - !ruby/object:Gem::Version
40
- version: 0.3.0
40
+ version: 0.3.1
41
41
  - !ruby/object:Gem::Dependency
42
42
  name: bundler
43
43
  requirement: !ruby/object:Gem::Requirement