V2024 API: Not respecting the Environment "domain" setting

Feedback Bugs
, , ,
1

What problem are you observing?

When trying to use the V2024 API with my Ambassador tenant in the “identitynow-demo” domain in Postman, I am getting an error. This only happens with the V2024 domain, and is not happening if I use the exact same environment for beta or V3.

Env_Postman
Env_Postman1446×196 7.41 KB

I tested with List Campaigns, List Identity Profiles and Get Tenant Info and I get the same error:

Error_Postman
Error_Postman825×309 13.4 KB

I verified that the pre-script in the Collection is the same, as well as the configured variables on the collection. Also verified that there are no other pre-scripts or variables set in either collection (V2024 and Beta) that would come into play. It is almost like the Variables in the collection (where ‘domain’ and ‘baseurl’ are initially configured are not respecting the domain configured from the pre-script.

What is the correct behavior?

The environment one should be used, but it is using the default

What product feature is this related to?

Postman Collection for the V2024 API for ISC

What are the steps to reproduce the issue?

Create an Enviroment for a tenant in the identityNow-demo domain.
Set that environment
Attempt to connect to an API.

Do you have any other information about your environment that may help?

none

2

Hi @gmilunich,

The variables are working for me with no issues.
Sometimes Postman acts funny and don’t load the variables in script. Did you tried restarting Postman?
image

3

I had restarted it before, but I will try it again.

4

I didn’t have the v2024 collection yet, so I did a fresh fork and it works fine for me with my existing environment variables. Maybe try deleting the collection and forking it again.

5

I just restarted Postman, but am seeing the same issue still occurring.

I am going to restart my computer after some meetings and will follow up if that made a difference.

6

I will try that is restarting it doesn’t help. I did pull the latest for the collection before creating the topic. After I try restarting the computer, I will pull a fresh copy of the collection if needed.

Thanks everyone.

7

I tried restarting Postman again but the issue persisted.

I did a pull changes and it said I was on the latest.

I re-forked the Postman collection from the api link and that is now working. The original still isn’t.

So it looks like it might be either an older version of the collection that I am stuck on, or my Postman/system having issues.

For now, @colin_mckibben was correct and this was resolved by re-forking the Postman collection.