M3 H5: IDM API call from M3 H5

Hello all,

I'm trying to call IDM API /infor/IDM/api/items/search/item/resource?/Control_Document[@Planned_Order = "1633"]from H5 script, however I received error HTTP 404 - Unauthorized.

I tried calling the same API in Postman and it returned the same error as well (please see the attached screenshot below).

It seem the API has some issue accessing /ca/api/items/..., why it is accessing it?
What is the proper way or how to call the IDM API from H5?

Note:
1. A valid token and parameter have supplied to the API.

Could anyone assist me on this issue? Thanks in advanced!

Regards,
YS

Find more posts tagged with

Accepted answers

Legacy Contributor

1. What type of valid token have you supplied? Is the port used for ION API? It seems like Infor ION Grid is refusing the call to IDM. But it's not a !role error message it's actually authentication that failed not authorization

3. M3 H5 is on another host and on an other grid and if the IDM proxy is installed you should use a relateive path starting with /ca to call it, but that will only work once the script is deployed in M3 H5.

Until then use the ION API tool within Mingle to try different requests instead of postman.

If you would like to test with Postman then you will have to call the ION API endpoint with a correct Bearer token as authorization, which you have tested. It seems like ION API is forwarding the request but grid still says HTTP401. Check the monitoring in ION API to get more information about the request that you are trying to do.

Regards

Karin

Legacy Contributor

Hi, So you were on an OnPrem installation of M3. With an on-prem installation you would have to use the proxy as there is no support for getting a valid token from the version of the ION Grid that M3 is running on (1.13.x).

With the proxy the grid session will be used to be able to call the proxy and the proxy is set-up with certificate. But the authentication against IDM I think is done through the certificate. I don't remember if the proxy had support for impersonation. You will need to check this in the documentation of the proxy.

All comments

Legacy Contributor

Until then use the ION API tool within Mingle to try different requests instead of postman.

Regards

Karin

Legacy Contributor

Hello Karin,

1. The Bearer token is copied from ION API (for testing only, to mimic the API call in Postman).

I've installed and configured the IDM proxy.
It's working now by calling the IDM API with relative path (https://<M3 Server>/ca/api/items) in M3 H5.

I notice that it doesn't required an authentication header in place for the API. Does it take the current user session for authenticate?

CROS reference: (explanation)

Thank you!

Regards,
YS

Legacy Contributor

Hi Karin,

Noted, I will check on the documentation.
BTW, thank you for the information and all the help!

Best regards,
YS

Copyright © 2025 Infor. All rights reserved.