Update: Turns out that the fusionauth/fusionauth-client libary does not seem to have support for specifying a tenantId field.

I rewrote my backend to use PHP's native cURL implementation and am back in business.

I am using the fusionauth/fusionauth-client PHP package, installed via Composer for my PHP backend API for my new VueJS + Webpack application. Everything works as expected using an existing FusionAuth server with the known working API key and Application ID.

But...

When I stand up a fresh FusionAuth server and create a new App and API key with same settings, my backend API is not getting the expected results. Instead, I get JSON response that yields no useful information about why I am unable to perform any API actions, such as login attempts, registering a user, etc.

The difference between old working and new non working FusionAuth servers is that in the new non-working server, I first created a Tenant, Created an App assigned to that Tenant, then created a couple users assigned to that App.

The old system uses the default Tenant and all my users are under that Tenant and it works totally fine.

I have looked all over the place for a solution to 1) dig into any logs to help me isolate the issue and 2) whether or not I may also need to specify a tenantID in my API requests.

Looking over the source code for the PHP client, I see nothing refering to this so I am lead to believe that only an API key and App ID are the only two things I need as well as the endpoint for the FusionAuth server.

I suspect that somehow, my App ID and/or App Key are silently being rejected but I am not getting any errors. Even went as far as standing up yet another server to try and replicate my old server only to have same issues.

Any ideas or direction would most certainly and greatly be appreciated.

Thanks!