MLuong | 2024-07-31 15:32:42 UTC | #1
Our org is needing to test Web Messenger Authentication in our lower lanes and our sit/stage enviroment discovery urls are not accessible externally so when attempting to setup the OIDC integration it throws the failed to fetch discocery uri error.
Is there a specific IP range that OIDC integration makes requests from that we can have our security team allow to work around this? Thank you.
Angelo_Cicchitto | 2024-08-07 09:40:23 UTC | #2
Hi @MLuong indeed we cannot limit the source IP address range, there’s a wider initiative based on this idea > https://genesyscloud.ideas.aha.io/ideas/OP-I-455
For this particular use-case, if you need a way to build custom rules on your firewall, perhaps we should explore custom HTTP headers rather than IP-address. Feel free to create an Idea for this. Thanks for reaching out.
MLuong | 2024-08-07 17:17:54 UTC | #3
Thanks for the response Angelo, rather than whitelisting IP addresses, do you know if there is a specific URL that Genesys would make this request from?
Angelo_Cicchitto | 2024-08-08 06:22:27 UTC | #4
We'll do some more research on this @MLuong and get back to you.
MLuong | 2024-08-19 02:26:19 UTC | #5
Hey Angelo, just wanted to see if there was any update so far. Thank you!
Angelo_Cicchitto | 2024-08-26 17:36:20 UTC | #6
Hello @MLuong at the moment the closest we can get to support your use-case would be to leverage ad-hoc content we added to User-Agent header: HTTP requests originating from Genesys Cloud Auth Client will include the value Genesys Auth-Client in User-Agent header. For more advanced customization, would recommend to raise an Idea in our portal as I mentioned earlier: possible research may happen via customizable header content or TLS certificates.
system | 2024-09-25 17:36:51 UTC | #7
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 27504