IAM 2.8.1 Release

InterSystems API Manager (IAM) version 2.8.1 is now Generally Available. In addition to a spade of performance improvements and bug fixes, this release adds significant new functionality, including:

After I loaded the intersystems/iam:0.34-1-1 image in local, I am trying to do the next step of configuration.

2) Configure your InterSystems IRIS instance

2a) Enable the /api/IAM web application
2b) Enable the IAM user
2c) Change the password for the IAM user

Do we need to change these settings in iris.cpf file? any inputs where we have to configure? I have IRIS 2019.1.1 installed in my machine.

Thanks,

Nag.

Hi Community!

Please welcome the new video on InterSystems Developers YouTube, recorded by @Patrick Jamieson:

⏯ InterSystems API Management and FHIR

https://www.youtube.com/embed/dlLFrxbQowk
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

We have solution which uses IRIS with IAM and webgateway integrated.

After integration, we notice that in the kong configuration in the kongdb upstreams are not created as listed in the kong.yml

We noticed that, IAM api calls are failing with enterprise license expired.

[kong@iam-deployment-75f485954c-ssdfv /]$ curl --location --request POST 'http://localhost:8001/services/'
{"message":"Enterprise license missing or expired"}

From Logs:

Hello!

Greetings from Chile, I have a question about IAM, I have a client who implements IAM in a QA environment, I configure a workspace and a series of routes (quite a few) and now he wants to export what has been created and take it to production (another server), which is the procedure to do it? Is it possible to export the workspace, routes, plugins, etc.?

Thank you!!

Has anyone else seen this error? From the API Manager Catalog, I can select an API and use the "Try it Out" feature. An error is returned - TypeError: Failed to fetch.

The same Curl can be imported into Postman and executed successfully. For us, API Manager is in a container and the container can ping the server. Also, this error is in the Developer Tools/Console -

My cluster status is as follows:

when I do journal restore on primary, it says journal restore is not allowed. The DR is also not allowed to do journal restore.

Hey Developers,

Watch this video to learn how UC Davis Health uses InterSystems API Manager to satisfy business-partner demand for access to both custom and FHIR APIs:

⏯ How UC Davis Health Uses InterSystems API Manager @ Global Summit 2023

https://www.youtube.com/embed/PJyIWOvntso
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

I downloaded IAM-3.4.2.0-5604.tar.gz from the Online Distribution site this morning, it the implementation to install it on our Development environment to see if it is a viable solution. Following the instructions, I have ran into an issue trying to make sure I am entering the information into the prompts correctly.

I have IRIS HealthShare Health Connect 2024.1 running locally using a Local Web Server, so when prompted I have entered the IP Address and port 443 is that correct?