IMS - Custom parameters not working?

Hi,

We are setting up an IMS communication with an external partner (Azure). To protect the Azure endpoint most often a “subscription key” is used as an extra security layer. However, this does not seem to work with the IMS endpoint setup in ION-API.

We are trying to set the “custom parameters” on the endpoint but it seems that this is not working at all. We don’t have possibility to see what has been sent from ION since the payload is not logged in ION.

Do anyone have any experience with this? When we deactivate the "subscription key" in Azure the communication works perfectly fine but when it is activated it is no longer working since Azure is not receiving the correct key. We have tried to use both the "header" and "Query" options without any luck.

Find more posts tagged with

ION API Gateway

Accepted answers

All comments

unknown

You can watch the payload in Cloud by going into ION API -> Monitoring -> Clicking on the "ION API Monitoring" element:

From there you can activate the payload monitoring

However, what you're configuring on your panel is the Authentication, what you want to do is to use Suite Policies to modify your Request Policy. You can find that inside of your custom API

unknown

Thanks,

For the payload - I have configured it as that already but where can I see the payload of each API-call?

The second point - that is true and probably the reason why it is not working. I am using the standard "Infor messaging service v3" and for this endpoint I don't see any possible to add any "Suite policies" or other "policies" at all. This only seems to be possible for non - infor standard connections.

I can also add that we are trying to implement this standard method - "IMS via API-Gateway". As I wrote it works fine until we add an extra security layer on the non-infor endpoint.

https://docs.infor.com/inforos/2023.x/en-us/useradminlib_cloud/default.html?helpcontent=ioncedg_cloud_osm/fje1624635398715.html

unknown

I found that for the detailed payload logging it needs to be requested from support to be activated. I have created the request. KB - 2319427

Kevin Heiman

Can you clarify, you are using ION Data Flow to invoke a IMS target that resides in Azure.

Is the use case that you have written the IMS Server side code, then configured a API Suite for the Azure IMS server endpoint. ION is then a client data flow using the API connection . ION will be the client and send data to the Azure IMS server.

If so that would be a customer endpoint and support policies. Maybe you are connecting to the ION IMS endpoint which would seem wrong and the reason for your issue. However the IMS endpoint from Infor would be private and you could not be adding in security. It is unclear from the images if this is a custom or ION .

Payload tracing is part of the second phase in API tracing, and is planned for April 2024 release. The feature to enable trace will likely give you what you need to see headers.

unknown

Some background -
Our use case is that we want to setup a communication between ION and our integration platform that is built in Azure. For this we are planning to use IMS (Infor Messaging service) protocol since it seems to be a good option that gives us what we are looking for.

We will both send and receive files from Azure through the IMS protocol.

ION --> Azure

Azure --> ION

We have followed the guides in the documentation - (IMS via API gateway) and it seems to work well. https://docs.infor.com/inforos/2023.x/en-us/useradminlib_cloud/default.html?helpcontent=ioncedg_cloud_osm/fje1624635398715.html

Back to your questions -

We have setup an connection point in ION that is of the type "IMS via API Gateway".
- Where we also define which "documents" that can be received and sent to the endpoint.
We have created the API-endpoints in Azure to manage the IMS protocol. So our Azure endpoint can handle the API-calls Ping/ Protocol / /v3/multipartMessage.
According to the documentation the Azure endpoints for IMS should then be configured in ION-API--> Authorized apps --> ION Messaging Service v3 API suite template

Add an available app using the ION Messaging Service v3 API suite template.
https://docs.infor.com/inforos/2023.x/en-us/useradminlib_cloud/default.html?helpcontent=ioncedg_cloud_osm/qof1625042510287.html

This is the issue since we are using the infor standard API Suite for IMS which is not possible to adjust with API policies.

Since this is not supported I guess we need to either skip the extra security layer or think of another communication protocol between ION and Azure.

unknown

Marcus,

I don't think the subscription key contributes to security over the OAuth 2 implementation in any substantial way, but it should be usable.

i think you should only use one method and I recommend header vs query: the documentation specifies "one of two ways" ...

Have you tested the target connection from a postman or some other tool? You might want to look at your azure gateway configuration - does your key have the correct scopes? is the key correctly associated with the targeted service?

Also, depending on your implementation you might try lower case ...shouldn't matter, but ...

e.g.

Good luck!

David

unknown

Thanks everyone for your feedback.

We will continue to do some testing but as of now we will just skip the "subscription key". As you mention OAuth 2.0 is sufficient in our use case. We just wanted to explore if it was possible to use.

I will update you if I find any solution to it! Thanks!

Copyright © 2025 Infor. All rights reserved.