Bug: Handle token refreshes when token is not present

[david-livefront]

🎟️ Tracking

N/A

📔 Objective

Stumbled upon a crash that can occur now that we allow optionally authenticated calls to be made. This means the access token might not be present when the authenticator is invoked (and that's OK)

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed a focused bug fix in AuthTokenManager.authenticate that replaces a crashing requireNotNull with a safe ?: return null when the Authorization header is absent. This handles the case where optionally-authenticated calls proceed without an access token, so a resulting 401 reaches the authenticator with no Bearer header. The new early-return matches the existing 401 pass-through pattern in the same method, and an accompanying unit test verifies the null path without triggering a token refresh.

Code Review Details

No findings. The fix is correct, minimal, and consistent with established patterns in the file. Test coverage appropriately exercises the new null-header path and asserts that refreshAccessTokenSynchronously is not invoked.

[david-livefront]

Thanks @SaintPatrck