Datasette-auth-tokens

Latest version: v0.3

Safety actively analyzes 613603 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.4a9

- Fixed a bug where the heading "Specific tables in specific databases" showed even for databases with no tables. [32](https://github.com/simonw/datasette-auth-tokens/issues/32)

0.4a8

- Fix for intermittent `database is locked` bug in managed tokens mode. [30](https://github.com/simonw/datasette-auth-tokens/issues/30)

0.4a7

- New `auth-tokens-create` permission governing whether users are allowed to create tokens. [24](https://github.com/simonw/datasette-auth-tokens/issues/24)
- New `auth-tokens-view-all` permission, granting users the ability to view tokens that they did not themselves create. [19](https://github.com/simonw/datasette-auth-tokens/issues/19)
- `auth-tokens-revoke-any` renamed to `auth-tokens-review-all`. [29](https://github.com/simonw/datasette-auth-tokens/issues/29)

0.4a6

- Fix for 500 bug if actors were not correctly returned. [23](https://github.com/simonw/datasette-auth-tokens/issues/23)

0.4a5

- Actors on the token listing page are now displayed using the [actors_from_ids](https://docs.datasette.io/en/latest/internals.html#datasette-actors-from-ids) mechanism, if available. [22](https://github.com/simonw/datasette-auth-tokens/issues/22)

0.4a4

Improvements to the create token page for managed token mode. [21](https://github.com/simonw/datasette-auth-tokens/issues/21)

- Don't show `permissions-debug` and `debug-menu`, since they don't make sense for API tokens to use.
- Include short descriptions of each permission.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.