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
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -176,6 +176,7 @@ The following settings are available for configuration in `config/initializers/d
176
176
|---|---|---|
177
177
|**`change_headers_on_each_request`**|`true`| By default the access-token header will change after each request. The client is responsible for keeping track of the changing tokens. Both [ng-token-auth](https://github.com/lynndylanhurley/ng-token-auth) and [jToker](https://github.com/lynndylanhurley/j-toker) do this out of the box. While this implementation is more secure, it can be difficult to manage. Set this to false to prevent the `access-token` header from changing after each request. [Read more](#about-token-management). |
178
178
|**`token_lifespan`**|`2.weeks`| Set the length of your tokens' lifespans. Users will need to re-authenticate after this duration of time has passed since their last login. |
179
+
|**`max_number_of_devices`**|`10`| Set the max number of concurrent devices per user. After this limit is reached, the oldest tokens will be removed. |
179
180
|**`batch_request_buffer_throttle`**|`5.seconds`| Sometimes it's necessary to make several requests to the API at the same time. In this case, each request in the batch will need to share the same auth token. This setting determines how far apart the requests can be while still using the same auth token. [Read more](#about-batch-requests). |
180
181
|**`omniauth_prefix`**|`"/omniauth"`| This route will be the prefix for all oauth2 redirect callbacks. For example, using the default '/omniauth' setting, the github oauth2 provider will redirect successful authentications to '/omniauth/github/callback'. [Read more](#omniauth-provider-settings). |
181
182
|**`default_confirm_success_url`**|`nil`| By default this value is expected to be sent by the client so that the API knows where to redirect users after successful email confirmation. If this param is set, the API will redirect to this value when no value is provided by the client. |
0 commit comments