Quay is showing 'Invalid bearer token format' error

Solution Verified - Updated -

Issue

  • Why is the mirror registry (Quay) showing the following logs
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout | 2024-02-21 23:06:04,354 [198] [DEBUG] [auth.registry_jwt_auth] Validating auth header: Basic xXyYzXxYuZzzzzw==
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout | 2024-02-21 23:06:04,355 [198] [ERROR] [auth.registry_jwt_auth] Invalid bearer token: Invalid bearer token format
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout | Traceback (most recent call last):
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout |   File "/quay-registry/auth/registry_jwt_auth.py", line 104, in identity_from_bearer_token
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout |     payload = decode_bearer_header(bearer_header, instance_keys, app.config)
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout |   File "/quay-registry/util/security/registry_jwt.py", line 50, in decode_bearer_header
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout |     raise InvalidBearerTokenException("Invalid bearer token format")
Feb 22 08:06:04 hostname podman[10552]: gunicorn-registry stdout | util.security.registry_jwt.InvalidBearerTokenException: Invalid bearer token format
Feb 22 08:06:04 dns01 quay-app[10579]: gunicorn-registry stdout |   File "/quay-registry/auth/registry_jwt_auth.py", line 104, in identity_from_bearer_token
Feb 22 08:06:04 hostname quay-app[10579]: gunicorn-registry stdout |     payload = decode_bearer_header(bearer_header, instance_keys, app.config)
....

Environment

  • Red Hat Quay (formerly Quay Enterprise)
  • OpenShift Container Platform 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content