AYON CPP API doesn't support using AYON serivce api key

[MustafaJafar]

Describe the bug

AYON CPP doesn't accept AYON_API_KEY.

Why is this an issue?

When working with DCC locally, the AYON_API_KEY is set to the bearer token.
On the other hand, when working with DCC on farm, the AYON_API_KEY is set to the service api key.

This cause the resolver to fail to login on farm jobs where the AYON_API_KEY is set to the service api key.

Describe yourself

No response

To Reproduce

No response

How did you discover the bug?

No response

Expected behaviour

No response

Screenshots

No response

Hardware Setup

No response

Software Setup

No response

User Type

No response

Additional Environment Details

No response

What platform are you running on?

Windows 11

Additional context

No response

Is there an existing issue with this?

• I have searched the existing issues

Are there any labels you wish to add?

• I have added the relevant labels to the bug report.

[MustafaJafar]

I think I've found out the cause...

In the main branch, It expects a bearar token with no usage of X-Api-Key (which is the one that accepts an API Key)

ayon-cpp-api/src/AyonCppApi/AyonCppApi.cpp

Line 81 in bb69957

m_AyonServer->set_bearer_token_auth(m_authKey);

and, in #35 it uses X-Api-Key but only if SSL is enabled and I don't have that in my home setup so, I fallback to the bearar token.

ayon-cpp-api/src/AyonCppApi/AyonCppApi.cpp

Lines 141 to 144 in 92c0eef

	if (isSSL()) {
	m_headers = {
	{"X-Api-Key", m_authKey},
	};

ayon-cpp-api/src/AyonCppApi/AyonCppApi.cpp

Lines 189 to 192 in 92c0eef

	} else {
	m_AyonServer->set_bearer_token_auth(m_authKey);
	m_headers = {};
	}

[MustafaJafar]

This issue was solved by #38 but it's part of #35. so when it's merged the solution will make it to the develop branch.