v0.3.12

Fix ExternalJWTAuthentication silently returning 403 instead of 401
DRF rewrites AuthenticationFailed/NotAuthenticated from 401 to 403
whenever no authenticator advertises a WWW-Authenticate challenge
header. ExternalJWTAuthentication never defined authenticate_header(),
so every expired/invalid token came back as 403 on any DRF backend
using this authenticator - silently breaking client refresh-on-401
ogic across every consuming service, not just one app.

Title: v0.3.11

Fix settings loader when Django is unconfigured; keep _is_django alias

Title: v0.3.10

made package imports framework-agnostic (no FastAPI required for Django)

Title: v0.3.8

Fixed DRF authentication behavior by returning an authenticated ClaimsUser to satisfy IsAuthenticated.

Added Gait cookie whitelist (access_token, refresh_token, temp_token) to avoid unnecessary /whoami/ calls from unrelated cookies.

Forward auth cookies only (smaller request surface, faster + safer).

Added explicit 503 handling when the Auth API is unavailable (distinct from invalid credentials).

Added stable import entrypoint auth_integration.authentication.ExternalJWTAuthentication to prevent DRF string-import breakage.

Added pytest coverage for DRF adapter:

no-credentials → None

bearer/cookie success paths

invalid token → 401

upstream outage → 503

shim import regression test

v0.3.6

final update hopefully

v0.3.5

updated persmissions, again

v0.3.4

updated project tomel

v0.3.1

updated incorrectly named permissions.

v0.3.0

updated init.py

v0.2.9

updated init.py to grab django dir modules