Hi Shah,
That's the only way I know of implementing your requirement. See https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=applications-working-global-policies on how to create and manage a global pre-hook policy. The example shows in the pre-hook policy an invoke policy, but you'd need a GatewayScript policy that met your requirement.
Best Regards,
Steve Linn
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------
Original Message:
Sent: Wed October 09, 2024 10:17 AM
From: Shah Wajahat
Subject: Client-Id client and client Secret
Yes but I don't have pre-hook global policy. Is there any other way?
------------------------------
Shah Wajahat
Original Message:
Sent: Wed October 09, 2024 09:27 AM
From: Steve Linn
Subject: Client-Id client and client Secret
Hi Shah,
If I understand the question, you want to have the client provide the clientid and secret using a custom HTTP header instead of X-IBM-Client-Id and X-IBM-Client-Secret. If so, you could have a pre-hook global policy that checked for the existence of these custom headers and if present, use them to update the X-IBM equivalent headers so the API behaves as if the X-IBM headers were provided up front.
Best Regards,
Steve Linn
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
Original Message:
Sent: Wed October 02, 2024 02:45 AM
From: Shah Wajahat
Subject: Client-Id client and client Secret
Hi team!
I want to consume custom client id and secret in native token api (like client-id:abcdBank123 and secret ancdbank321 ) instead of using APIC client id and secret which is generated during created application .
Any one help me about this or any documentation related to this.
------------------------------
Shah Wajahat
------------------------------