Issue confirmed by our auth provider, waiting for root cause. A configuration update caused some legitimate authentication-related requests to be incorrectly blocked.

The issue seems to be resolved