---
title: "Comment by Vaughan Brown on \"Access ATP APEX using a Reverse Proxy\" | Hashnode"
description: "Hi Matt, thanks for the cool article - I&#39;ll be trying it out within the next few days. I can see you mentioned that SSO wouldn&#39;t work with this. Can you"
url: "https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/635175677aeee8b5d0781de9"
---

[Discussion](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466)

Comment [Access ATP APEX using a Reverse Proxy](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466)

[Vaughan Brown](https://hashnode.com/@vaughan)

[Oct 20, 2022](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/635175677aeee8b5d0781de9)

Hi Matt, thanks for the cool article - I'll be trying it out within the next few days.

I can see you mentioned that SSO wouldn't work with this. Can you confirm if other API calls would work - such as an API request to PayPal?

[Matt Paine](https://hashnode.com/@mattpaineintexas)

[Nov 1, 2022](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/635175677aeee8b5d0781de9#reply-63616a4d9bf8a6729b5a2cb0)

Hi - other outbound calls should have no issues; the problem for Social Sign On and SSO is that ORDS passes a callback URL to SSO which doesn't match the reverse proxy - bit of a specialized exception. There's no mechanism to change this that I'm aware of. Otherwise, all should be well.
