1.0a1

• Fix for bug: AttributeError: 'Datasette' object has no attribute '_auth_existing_cookies_cache' #19

1.0a0

This alpha release breaks backwards compatibility, and completely redesigns how this plugin works. #13

• Plugin now uses the actor_from_request() plugin hook
• Implementation is greatly simplified: the forbidden mechanism and redirect to login via a signed next= parameter components have been removed
• Plugin configuration settings have been renamed, see the README

0.7

• Respects scope["auth"] if it has already been populated by another authentication plugin - #12

0.6.1

If you are running multiple Datasette plugins this plugin will now attempt to go last and wrap all of the other plugins, ensuring they too will be protected by authentication.

0.6

The previous release always forwarded the ?host= header on to the authentication API. This release no longer does that by default, but instead allows you to configure one or more headers that should be passed on in a similar way - issue #10.

To get back the same behavior as release 0.5, use this configuration:

{
    "plugins": {
        "datasette-auth-existing-cookies": {
            "api_url": "http://www.example.com/user-from-cookies",
            "auth_redirect_url": "http://www.example.com/login",
            "original_cookies": ["sessionid"],
            "headers_to_forward": ["host"]
        }
    }
}

0.5.1

Fix error triggered by combining this plugin with datasette-upload-csvs.

0.5

• New trust_x_forwarded_proto configuration setting to fix issues with the incorrect ?next= URL being generated when running behind a proxy that adds https://. #8
• The api_url used to check the user's identity can now also perform permission checks, returning {"forbidden": "Reason string here"} if the authenticated user should not be allowed access to the Datasette instance specified by the ?host= parameter. #9 - documentation here: https://github.com/simonw/datasette-auth-existing-cookies/blob/master/README.md#permissions

0.4.1

Fixed error caused by host= URL construction.

0.4

The API URL is now called with a ?host=blah.example.com argument, allowing the underlying API to make permission decisions based on the host.

0.3

First non-beta release.