UPDATE dependencies / skipForceSessionSave

florianheinemann · Jun 18, 2015 · 4584ee6 · 4584ee6
1 parent 73d2dec
commit 4584ee6
Show file tree

Hide file tree

Showing 44 changed files with 13,225 additions and 1,776 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,16 @@
+# 1.1.0 (2015-06-18)
+
+Bugfixes:
+- N/A
+
+Features:
+- ADD option.skipForceSessionSave to support cookie-session middleware
+- UPDATE to latest dependencies
+- UPDATE example to work with latest dependencies
+
+Documentation:
+- N/A
+
 # 1.0.9 (2015-02-14)
 
 Bugfixes:

diff --git a/README.md b/README.md
@@ -89,7 +89,7 @@ app.use(passwordless.sessionSupport());
 app.use(passwordless.acceptToken({ successRedirect: '/'}));
 ```
 
-`sessionSupport()` makes the login persistent, so the user will stay logged in while browsing your site. Make sure to have added your session middleware *before* this line. Have a look at [express-session](https://github.com/expressjs/session) how to setup sessions if you are unsure.
+`sessionSupport()` makes the login persistent, so the user will stay logged in while browsing your site. Make sure to have added your session middleware *before* this line. Have a look at [express-session](https://github.com/expressjs/session) how to setup sessions if you are unsure. Please be aware: If you decide to use [cookie-session](https://github.com/expressjs/cookie-session) rather than e.g. express-session as your middleware you have to set `passwordless.init(tokenStore, {skipForceSessionSave:true})`
 
 `acceptToken()` will accept incoming tokens and authenticate the user (see the URL in step 5). While the option `successRedirect` is not strictly needed, it is strongly recommended to use it to avoid leaking valid tokens via the referrer header of outgoing HTTP links. When provided, the user will be forwarded to the given URL as soon as she has been authenticated.