This pull request removes the need for the req and pay in the claims JWT.

Use the new version of the notifications-python-client. This version no longer adds the req and pay to the claims of the jwt.

The change is backward compatible so an older client that sends a JWT with the extra claims will pass authentication.
Once all the clients have been updated to not include the extra claims some updates to exclude them from the method signatures will happen as well.

The documentation has been updated to reflect this change.

https://www.pivotaltracker.com/story/show/116971293

app/templates/views/documentation.html

@@ -48,26 +48,10 @@
 {
   iss: 'string', // service id
   iat: 0, // creation time in  epoch seconds (UTC)
-  req: 'string', // signed request
-  pay: 'string', // signed payload (POST requests only)
 }
         """|syntax_highlight_json}}
 <div class="grid-row">
     <div class="column-three-quarters">
-        <p>Notify API tokens sign both the request being made, and for POST requests, the payload.</p>
-
-        <p>
-            The signing algorithm is HMAC signature, using provided key SHA256 hashing algorithm.
-        </p>
-
-        <p>Request signing is of the form HTTP METHOD PATH.</p>
-
-        {{ "GET /notification/1234"|syntax_highlight_json }}
-
-        <p></p>
-
-        <p>Payload signing requires the actual payload to be signed, NOT the JSON object. Serialize the object first
-            then sign the serialized object.</p>
 
         <h3 class="heading-medium">
             API endpoints