---
title: "Comment by Jon Dixon on \"Access ATP APEX using a Reverse Proxy\" | Hashnode"
description: "Excellent. Just confirming that you don’t need to install customer managed ORDS, just point to the ATP URL?"
url: "https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/63358134e594fa4ba3b8c1a6"
---

[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)

[Jon Dixon](https://hashnode.com/@orclapex)

[Sep 29, 2022](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/63358134e594fa4ba3b8c1a6)

Excellent. Just confirming that you don’t need to install customer managed ORDS, just point to the ATP URL?

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

[Oct 10, 2022](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/63358134e594fa4ba3b8c1a6#reply-634430576d64be07a724aa91)

Hey Jon - you don't have to use customer-managed ORDS in this use-case, however, one of the things I'm finding is that the approach above breaks Social Sign-on. So if that's a requirement, you're into customer-managed ORDS territory. See the "Epilogue" above.

[Jon Dixon](https://hashnode.com/@orclapex)

[Oct 10, 2022](https://hashnode.com/posts/access-atp-apex-using-a-reverse-proxy/633353822ee4a479cbc2d466/comment/63358134e594fa4ba3b8c1a6#reply-63443d9af943840715bd210c)

Thanks for clarifying.
