Getting 401 Unauthorized, but everything seem in place

[maxxer]

Hi.
I've been successfully testing Mercure in local development with Docker. We're running a Symfony 6.4 app and Mercure in a Docker Compose environment.

The env vars for Mercure service are:

SERVER_NAME: ':7999'
PORT: 7999
MERCURE_PUBLISHER_JWT_KEY: '!MercureDevelopmentSigningKeyLongEnough!'
MERCURE_SUBSCRIBER_JWT_KEY: '!MercureDevelopmentSigningKeyLongEnough!'
MERCURE_EXTRA_DIRECTIVES: 'cors_origins https://app.domain.local'

On the client side, we subscribe to topics with:

		window.eventSource = new EventSource(
				"{{ mercure(getMercureSubscribedTopics(), {'subscribe': getMercureSubscribedTopics()})|escape('js') }}",
				{
					withCredentials: true
				});

Now, porting this to staging on Google Cloud returns 401. The Troubleshooting page says the log should explain why such a response is given, but I'm unable to find such a statement. Even adding DEBUG=debug or MERCURE_EXTRA_DIRECTIVES=debug to the environment variable doesn't change the output I get on the GCP Cloud Run service.

We have the following variables assigned to the container:

• SERVER_NAME: :80
• MERCURE_SUBSCRIBER_JWT_KEY
• MERCURE_PUBLISHER_JWT_KEY

Mercure is served through a Load Balancer service, proxying /.well-known/mercure to the service. In the logs, I get the requests and I see the 401 reply, although with no explaination.

I checked the client request on the browser's console, the JWT token is provided. I checked with jtw.io, the token is valid, and the signature matches the secret.
I double-checked the secret and it's correct on both sides, the client and the Mercure service.
I tried adding MERCURE_EXTRA_DIRECTIVES=cors_origins https://my.staging.domain.com (albeit the error not being related to CORS), but same result.

I don't know what else to look for. How can I obtain more information from the Mercure container/service? thanks

[maxxer]

In the end, it was probably something related to the secret. I change the value, removing I can't recall if the ! or ? values, and now the subscribe is successful!