{"id": "authentication:logoutview", "page": "authentication", "ref": "logoutview", "title": "The /-/logout page", "content": "The page at  /-/logout  provides the ability to log out of a  ds_actor  cookie authentication session.", "breadcrumbs": "[\"Authentication and permissions\", \"The ds_actor cookie\"]", "references": "[]"}
{"id": "authentication:authentication-ds-actor-expiry", "page": "authentication", "ref": "authentication-ds-actor-expiry", "title": "Including an expiry time", "content": "ds_actor  cookies can optionally include a signed expiry timestamp, after which the cookies will no longer be valid. Authentication plugins may chose to use this mechanism to limit the lifetime of the cookie. For example, if a plugin implements single-sign-on against another source it may decide to set short-lived cookies so that if the user is removed from the SSO system their existing Datasette cookies will stop working shortly afterwards. \n                 To include an expiry pass  expire_after=  to  datasette.set_actor_cookie()  with a number of seconds. For example, to expire in 24 hours: \n                 response = Response.redirect(\"/\")\ndatasette.set_actor_cookie(\n    response, {\"id\": \"cleopaws\"}, expire_after=60 * 60 * 24\n) \n                 The resulting cookie will encode data that looks something like this: \n                 {\n  \"a\": {\n    \"id\": \"cleopaws\"\n  },\n  \"e\": \"1jjSji\"\n}", "breadcrumbs": "[\"Authentication and permissions\", \"The ds_actor cookie\"]", "references": "[]"}