Authentication not working with Dedicated HTTP configuration

[clablancherie-exo]

Authentication not working with Dedicated HTTP configuration

Environment

• Package Version: 3.1
• Configuration: Dedicated HTTP
• Laravel Version: 12

Problem Description

When attempting to call a tool using the Dedicated HTTP configuration, authentication doesn't seem to be carried over. The result returns null, but the server doesn't stop and we don't receive any error logs or other indicators of what's going wrong.

Expected Behavior

Authentication should work seamlessly with the Dedicated HTTP configuration, allowing tools to be called with proper authentication context.

Actual Behavior

• Get Me Tool calls return null
• No error logs are generated
• Server continues running without any indication of authentication failure
• Authentication appears to be completely bypassed

Investigation Attempts

I've thoroughly explored the documentation but cannot understand how to properly pass authentication and middlewares to the Dedicated HTTP configuration section.

Request

Could you please provide more detailed documentation or examples on how to properly handle authentication with the Dedicated HTTP system? This is particularly important since this configuration is recommended for both development and production environments.

Additional Context

This issue is blocking our ability to use the recommended Dedicated HTTP configuration in production, as authentication is critical for our use case.

Thank you for your assistance!

[odtcfeliperamos]

Same

[xiaoxigithub]

I also encountered this issue, unable to retrieve the API Token Authentication from the request header, which prevents user authentication

[clablancherie-exo]

Hi @CodeWithKyrian,

Is it possible to have an update for this issue ?

Thanks