# IdP redirect URI and reverse proxy with SSL offloading

**URL:** <https://forum.inductiveautomation.com/t/idp-redirect-uri-and-reverse-proxy-with-ssl-offloading/44534>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 16, 2021, 4:30pm UTC](https://forum.inductiveautomation.com/t/idp-redirect-uri-and-reverse-proxy-with-ssl-offloading/44534 "2021-03-16T16:30:01Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [July 14, 2021, 11:36pm UTC](https://forum.inductiveautomation.com/t/idp-redirect-uri-and-reverse-proxy-with-ssl-offloading/44534/5 "2021-07-14T23:36:48Z")

</div>

Additionally, what versions are you attempting to use? The Designer Launcher in 8.1.7 now goes directly to `/StatusPing` for checking the connection where it previously hit `/main/StatusPing` and the redirect from the gateway tried to redirect to HTTP and was thusly rejected due to downgrade. See this thread for reference: [Hard coded request for HTTP in Designer Launcher even if gateway set up for HTTPS - #11 by kcollins1](http://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027/11)

The feature @jspecht references will definitely help smooth the experience out and address some of the other issues (related to client IP reporting).

---

_[View the full topic](https://forum.inductiveautomation.com/t/idp-redirect-uri-and-reverse-proxy-with-ssl-offloading/44534)._