You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Or install it yourself as:
29
29
`~> 0.3` | `~> 3.4.0`
30
30
`~> 0.4.0`, `< 0.4.9` | `~> 3.5.0`, `< 3.5.2`
31
31
`~> 0.4.9` | `~> 3.5.2`
32
-
`~> 0.5.x` | `>= 4.0.0`, `< 4.4.0`
32
+
`~> 0.5.x`, `<= 1.0.0` | `>= 4.0.0`, `< 4.4.0`
33
33
34
34
## Usage
35
35
@@ -66,6 +66,19 @@ Devise::TokenAuthenticatable.setup do |config|
66
66
end
67
67
```
68
68
69
+
Enable devise's HTTP Auth for the token strategy as shown below:
70
+
71
+
```ruby
72
+
# initializers/devise.rb
73
+
Devise.setup do |config|
74
+
# ...
75
+
config.http_authenticatable =true
76
+
# or
77
+
config.http_authenticatable = [:token]
78
+
# ...
79
+
end
80
+
```
81
+
69
82
## Troubleshooting
70
83
71
84
##### Using a new user's auth token does not result in invalidating an old users session. How can I ignore session storage when using token authentication?
0 commit comments