First cut at import of quick tutorial.

1 files changed, 134 insertions, 0 deletions

diff --git a/docs/quick_tutorial/authentication.rst b/docs/quick_tutorial/authentication.rst
new file mode 100644
index 000000000..6b9b5fafc
--- /dev/null
+++ b/docs/quick_tutorial/authentication.rst
@@ -0,0 +1,134 @@
+==============================
+20: Logins With Authentication
+==============================
+
+Login views that authenticate a username/password against a list of
+users.
+
+Background
+==========
+
+Most web applications have URLs that allow people to add/edit/delete
+content via a web browser. Time to add
+:ref:`security <security_chapter>`
+to the application. In this first step we introduce authentication.
+That is, logging in and logging out using Pyramid's rich facilities for
+pluggable user storages.
+
+In the next step we will introduce protection resources with
+authorization security statements.
+
+Objectives
+==========
+
+- Introduce the Pyramid concepts of authentication
+
+- Create login/logout views
+
+Steps
+=====
+
+#. We are going to use the view classes step as our starting point:
+
+   .. code-block:: bash
+
+    (env27)$ cd ..; cp -r view_classes authentication; cd authentication
+    (env27)$ python setup.py develop
+
+#. Put the security hash in the ``authentication/development.ini``
+   configuration file as ``tutorial.secret`` instead of putting it in
+   the code:
+
+   .. literalinclude:: authentication/development.ini
+    :language: ini
+    :linenos:
+
+#. Get authentication (and for now, authorization policies) and login
+   route into the :term:`configurator` in
+   ``authentication/tutorial/__init__.py``:
+
+   .. literalinclude:: authentication/tutorial/__init__.py
+    :linenos:
+
+#. Create a ``authentication/tutorial/security.py`` module that can find
+   our user information by providing an *authentication policy callback*:
+
+   .. literalinclude:: authentication/tutorial/security.py
+    :linenos:
+
+#. Update the views in ``authentication/tutorial/views.py``:
+
+   .. literalinclude:: authentication/tutorial/views.py
+    :linenos:
+
+#. Add a login template at ``authentication/tutorial/login.pt``:
+
+   .. literalinclude:: authentication/tutorial/login.pt
+    :language: html
+    :linenos:
+
+#. Provide a login/logout box in ``authentication/tutorial/home.pt``
+
+   .. literalinclude:: authentication/tutorial/home.pt
+    :language: html
+    :linenos:
+
+#. Run your Pyramid application with:
+
+   .. code-block:: bash
+
+    (env27)$ pserve development.ini --reload
+
+#. Open ``http://localhost:6543/`` in a browser.
+
+#. Click the "Log In" link.
+
+#. Submit the login form with the username ``editor`` and the password 
+   ``editor``.
+
+#. Note that the "Log In" link has changed to "Logout".
+
+#. Click the "Logout" link.
+
+Analysis
+========
+
+Unlike many web frameworks, Pyramid includes a built-in (but optional)
+security model for authentication and authorization. This security
+system is intended to be flexible and support many needs. In this
+security model, authentication (who are you) and authorization (what
+are you allowed to do) are not just pluggable, but de-coupled. To learn
+one step at a time, we provide a system that identifies users and lets
+them log out.
+
+In this example we chose to use the bundled
+:ref:`AuthTktAuthenticationPolicy <pyramid:authentication_module>`
+policy. We enabled it in our configuration and provided a
+ticket-signing secret in our INI file.
+
+Our view class grew a login view. When you reached it via a GET,
+it returned a login form. When reached via POST, it processed the
+username and password against the "groupfinder" callable that we
+registered in the configuration.
+
+In our template, we fetched the ``logged_in`` value from the view
+class. We use this to calculate the logged-in user,
+if any. In the template we can then choose to show a login link to
+anonymous visitors or a logout link to logged-in users.
+
+Extra Credit
+============
+
+#. What is the difference between a user and a principal?
+
+#. Can I use a database behind my ``groupfinder`` to look up principals?
+
+#. Do I have to put a ``renderer`` in my ``@forbidden_view_config``
+   decorator?
+
+#. Once I am logged in, does any user-centric information get jammed
+   onto each request? Use ``import pdb; pdb.set_trace()`` to answer
+   this.
+
+.. seealso:: :ref:`pyramid:security_chapter`,
+   :ref:`AuthTktAuthenticationPolicy <pyramid:authentication_module>`