-
Notifications
You must be signed in to change notification settings - Fork 8
Rails documentation in sphinx #57
Conversation
…thentication specs
… SDK documentation links
docs/authentication.rst
Outdated
|
||
If you are building a web application that serves traditional HTML pages, or a | ||
Single Page Application (Angular/React), this library will handle the cookie | ||
sessions for you. No special configuration is necessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cookies for you*
sessions for you. No special configuration is necessary. | ||
|
||
To use cookie authentication, simply use the ``require_authentication!`` before callback: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
before action*
docs/authentication.rst
Outdated
|
||
Here is an example configuration block, with the default settings: | ||
|
||
.. code-block:: ruby |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code-block should be yaml, not ruby.
docs/authentication.rst
Outdated
Token Validation Strategy | ||
......................... | ||
|
||
When a request comes into your server, this gem will use the Access Token |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to your server*
docs/authentication.rst
Outdated
|
||
Opt-in to ``stormpath`` validation with this configuration: | ||
|
||
.. code-block:: ruby |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same thing with code-block. Please change it in all places needed.
docs/authentication.rst
Outdated
authorization and security, this strategy should be used. In this situation | ||
the developer does a one-time exchange of their API Keys for an Access Token. | ||
This Access Token is time limited and must be periodically refreshed. This adds a | ||
layer of security, at the cost of being less simple than HTTP Basic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would use more complex instead of less simple :)
- Use Faker to generate random test data | ||
- Rename all user instances to account | ||
|
||
Released on Aug 22, 2016 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't a Version 2.0.1
be placed on top of this?
Comments fixed @DamirSvrtan |
PR for #48