[Bug]: Data Hub (v1.5.4) seems to break when using multiple API Keys in GraphQL API configuration

[khenow1978]

Expected behavior

When the user configures a GraphQL API to use several API Keys it's supposed to accept any of these key as authentification and returns the JSON result of the query.

Actual behavior

Within the GraphiQL Playground all Keys are smashed together to one large key and the API doesn't work correctly:

The Playground mentions this error message:

I have undone these changes in order to return to the state before but that doesn't work either. In fact NO API works anymore.. even if I create a new one with only one key. They all return HTML code instead of JSON.

So I did some further testing with a small Python script I wrote for this purpose:

As you can see it returns HTML code (that is in fact the Login Page from the Portal Engine) although I sent a proper query. When I exchange the transport with the production system API it works fine.

Even the connection itself isn't working properly anymore. In production when I forget to send the API Key I receive HTTP 400 but in the dev environment the result is always HTTP 200. That's not making a lot of sense to me.

I have upgrade from v1.5.4 to v1.5.8 in order to see if this resolves the issue. It didn't. Currently we are using Pimcore 10.5.14. The only short term solution would be to install Pimcore from scratch as Dev environment and start all over and see if the issue occurs once again.

Steps to reproduce

• Create a new GraphQL API

• Add several API Keys to the security section

• Save the API

• Try to use the GraphiQL Playground OR

• Try to access the API from an external source

[khenow1978]

After I've installed Pimcore once again, I've tried to reproduce the error but it didn't happen. Now the behaviour is as expected besides one issue which remains. Let's say you've created an API with 3 Keys:

Now, when you start the playground this happens:

All 3 Keys are smashed together to one string rather than an array (is this even possible as X-API-KEY??) and you get a permission error (Importan. NOT a DocType error). The solution is to take one of the 3 Keys from the API and replace the wrong key with the correct one:

Now it works.. I'm not sure if this is an expected behaviour because everytime you want to use the playground you have to keep in mind to replace the API Key..

[dvesh3]

Fixed by #795