How to set dynamic bearer token in ION API?

Hi,

We have registered API in ION API which requires Authorization of Type Bearer Token (Bearer token is obtained by calling another API). In ION API, We have set Target Endpoint Security as Anonymous because there is no option for Bearer Token. We are using Endpoint Policy instead. We have set the Request Policy with PolicyType as Header and Header Value is set as below.

<header
xmlns="">http://www.infor.com/ion/api"
xmlns:xsi="">www.w3.org/.../XMLSchema-instance" name="header-example" displayName="header-example" enabled="true" version="1.0">
<action>set</action>
<headerName>Authorization</headerName>
<headerValue>Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1bmlxdWVfbmFtZSI6Imphc3VqYUBnb2RyZWouY29tIiwic3ViIjoiVlI4czM1OS94UmpZclJMNnRESm1GZz09Iiwic2VydmVyIjoidlpkalhNSXhaZG1JTVlxR1VFaFdPanFuZ2FaMjVUT1lMTkJ4L2xBK1FRM3h4ditoTnQvYm9CVmVMTDhOc1NhWSIsImp0aSI6ImYzYzdjMTA5LWZiNjAtNGI4ZS04NDQ5LTU1NmYzNDg4OTFlOSIsIm5iZiI6MTY1MDcxOTAwMCwiZXhwIjoxNjUwNzIyNjAwLCJpYXQiOjE2NTA3MTkwMDAsImlzcyI6IlNlbGxlckNsb3VkIiwiYXVkIjoiU2VsbGVyQ2xvdWQifQ.QGtsHGMM412oB85C_PJzHf3cg5yR3TCKJlEhCbKw1sw</headerValue>
</header>

Howerver, the token is valid only for 1 hour. So every 1 hour, we need to get new token and pass it to this API. Hence, we cannot hardcode the token value. In ION API Administration Guide, I found the option to set header value as shown below. But I am not aware how to set this variable.

<headerValue ref=&#39;context.url.tenant&#39;/><br /><br />Have you come across such requirement? If so, can you please help how to achieve this?<br /><br />Thanks in advance.

Find more posts tagged with

API Usage

Accepted answers

All comments

unknown

Hi, I don't know the question to your answer but isn't there a way in ION API to create an orchestration of API calls. That way you would call the first to get the token and then the second in a flow. Have you checked the documenation for that option?

Daniel Henningsver

Hi, Is this an external API? It sounds like the endpoint security is Oauth2 and using Bearer. Then you should setup the Target Endpoint Security as Oauth 2.0 and then n the settings define how you retrieve the token (there are some different ways in Oauth to retreive the token). Once you have configured this, ION API will handle the token before sending the request and make sure it is valid. If the token is no longer valid, a request for a new token will automatically be done.

Ajay Dalvi

Hi DaHen. Yes, this is an external API. Yes, we tried opting for Target Endpoint Security as Oauth 2.0 and went for the "JWT Bearer Token" functionality in that option, but we are facing issues in that as my API is getting failed to fetch the token, we tried finding documentation on it so as to see where we are making a mistake in the configuration but couldn't get anything.

And hence we opted for 'Endpoint Policies', it would be great if we can get results in either of the ways.

unknown

I can understand that you want to Dynamically refresh/re-create auth token after 60minutes. This option is not available in ION API, re-creation of Auth token has to be handled in ION API calls from ION Desk or External Programs.

Daniel Henningsver

Ok, in my case I had username + password and a token from the external provider. the token was a base64 encoded string with client id and client secret separated by ":". Then I had all the information (User name, password, client id and client secret) which was needed in order to configure it. But if your external provider uses the JWT Bearer Token, I'm afraid I don't know how that works.

0909090854053232.pdf

Rene Bottern

One way, which I have done a couple of times, is to create your own RESTFUL API instance in .Net on a local IIS instance, and then have the logic in there to 'renew bearer key' when applicable before calling the external API.

This is not ideal, but gives you full control over how the communication is handled against your external API's.

David TOLLET

Hi Godrej,

I'm in the exact same situation as you.

How did you manage to sort this out ?

Many thanks.

Copyright © 2025 Infor. All rights reserved.