Potentially this is a just me issue but has anyone else experienced issues connecting to a production instance of IdentityNow via the Postman web interface? I have set up the collections via desktop and can connect to both my production and non-production instances with no issues on desktop. When I go to web.postman.co I can use the exact same connections, scripts, etc. for non-production, but for production I get that the client credentials are bad every time. I have generated new PATs and that doesn’t change the error. I’m not sure if I’m missing a security configuration that is blocking the connection in production, any help would be appreciated.
Depending on how your credentials are saved, Postman has different ways to sync variable across instances. If that is not the issue, is there an error message you are seeing from IDN?
Do you have a whitelist of IP addresses set up in your production env?
The same CIDR blocks are set in both environments, but I agree that was a good place to look.
Where would I look to find an error message like that?
Are the same client id and secret being used in both instances - Desktop and Web? Can you share the response you are getting?
As a test I opened up a very wide range of IPs, seeing as postman.co uses a wide range for connections. I was able to connect to production with this open. I’ll have to see if I can find a list of postman.co outbound connecting IPs to try and whitelist them. Thanks again for this suggestion!
1 Like
Good to know my reply helped you going in the right direction 
About IP addresses, I would rather disable the IP white list in the tenant (and enable it back once you are done) whenever you are using the Postman web interface as it might be hard to keep a track of the IP addresses the Postman server will be using
Agreed. The list is based on the AWS regional lists which makes opening to all of those a bit of a non-starter with my security team.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.