# Azure SSO Issue

**URL:** <https://forum.pritunl.com/t/azure-sso-issue/591>\
**Category:** Pritunl VPN\
**Tags:** pritunl\
**Created:** [December 5, 2022, 8:12pm UTC](https://forum.pritunl.com/t/azure-sso-issue/591 "2022-12-05T20:12:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JustBen](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/j/dc4da7/32.png) [@JustBen](https://forum.pritunl.com/u/JustBen)\
**Post date:** [December 5, 2022, 8:12pm UTC](https://forum.pritunl.com/t/azure-sso-issue/591/1 "2022-12-05T20:12:18Z")

</div>

HI,  
We just signed up for the enterprise. Almost 100% just for the SSO 🙂  
I followed the steps (2 twice now) for setting up Azure SSO and get the same error.  
I open an incognito mode, go to my URL, click “Sign in with Azure”  
It spins for a bit and then comes to “pritunl-vpn’s server ip address could not be found”  
Looking for a bit here, I see the url looks like this:  
[https://pritunl-vpn/sso/callback?state=TekxyJ](https://pritunl-vpn/sso/callback?state=TekxyJ)…

So I think I have something not configured correctly. But not sure what. A bit of explanation on my setup:

1. to access the web url through the outside world I am going through nginx, and a non-standard port (https : // [my.org.com](http://my.org.com): 444 )

I have tried restarting the server a few times, and I have tried rebuilding the secret keys and such.  
I have found that if I put the WRONG secret key in, it will give me a different error. So it seems something is working.

Also, why is it we are pointing call backs to auth pritunl com and not our own server? Are you somehow in the middle of the callback system? wouldn’t that be an inherit security risk?

Thanks!

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [December 6, 2022, 2:19am UTC](https://forum.pritunl.com/t/azure-sso-issue/591/2 "2022-12-06T02:19:07Z")

</div>

The Host header is used for the callback URL, the Nginx server may be modifying this. Single sign-on is handled through [auth.pritunl.com](http://auth.pritunl.com) this protects the enterprise features. Duo can be added as an additional separate layer of authentication that is not handled through the Pritunl authentication servers.

---

<div class="post-metadata">

**Author:** ![JustBen](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/j/dc4da7/32.png) [@JustBen](https://forum.pritunl.com/u/JustBen)\
**Post date:** [December 6, 2022, 4:43pm UTC](https://forum.pritunl.com/t/azure-sso-issue/591/3 "2022-12-06T16:43:56Z")

</div>

Hi Zach,  
That worked, it was the host header. Now we are running into an additional issue.  
I will start a new thread for that!
