Open APIs

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

Hello Prasan,

I encountered the same issue while testing with CTK. However, after switching from the token to an API key, everything started functioning as expected. 

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

Thanks Ragavi. Let me check and come back.

Hello Prasan,

I encountered the same issue while testing with CTK. However, after switching from the token to an API key, everything started functioning as expected. 

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

Hello Prasan,

I encountered the same issue while testing with CTK. However, after switching from the token to an API key, everything started functioning as expected. 

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

Hi Ragavi, Can you share the steps to switch from token to API key ?

Hello Prasan,

I encountered the same issue while testing with CTK. However, after switching from the token to an API key, everything started functioning as expected. 

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

Hi all,

I have completed testing the TMF629 with V4 conformance, following the steps outlined in the README.md. This involved modifying the URL, including the API key in the headers of the config.json file, and updating the payload as required.

Hi Ragavi, Can you share the steps to switch from token to API key ?

Hello Prasan,

I encountered the same issue while testing with CTK. However, after switching from the token to an API key, everything started functioning as expected. 

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

Thanks, Ragavi. We were able to get it working through both token and API key with V4 conformance now. Version 5.0 is still not working though with authorization.

------------------------------
Prasan Kumar
FSM Global Technologies FZ LLC

Original Message:
Sent: Oct 24, 2024 05:59
From: Ragavi Ramasamy
Subject: TM Forum 629 Version 5 API Test cases failing while using Authorization Token

Hi all,

I have completed testing the TMF629 with V4 conformance, following the steps outlined in the README.md. This involved modifying the URL, including the API key in the headers of the config.json file, and updating the payload as required.

------------------------------
Ragavi Ramasamy
Halleyx Inc.

Original Message:
Sent: Oct 23, 2024 04:30
From: Venkata Jonnalagadda
Subject: TM Forum 629 Version 5 API Test cases failing while using Authorization Token

Hi Ragavi, Can you share the steps to switch from token to API key ?

------------------------------
Venkata Jonnalagadda
AT&T Inc.

Original Message:
Sent: Oct 22, 2024 02:44
From: Ragavi Ramasamy
Subject: TM Forum 629 Version 5 API Test cases failing while using Authorization Token

Hello Prasan,

I encountered the same issue while testing with CTK. However, after switching from the token to an API key, everything started functioning as expected. 

------------------------------
Ragavi Ramasamy
Halleyx Inc.

Original Message:
Sent: Oct 21, 2024 10:59
From: Prasan Kumar
Subject: TM Forum 629 Version 5 API Test cases failing while using Authorization Token

While testing the APIs using Postman with the authorization token, everything is functioning as expected, and the output is correct. However, when running the CTK tests with the authorization token passed in the header, all tests are failing, despite running successfully without the token. Could you kindly confirm whether the authorization token needs to be passed in the header while running CTK tests, or if it is acceptable to execute them without the token?

------------------------------
Prasan Kumar
FSM Global Technologies FZ LLC
------------------------------