# Pritunl Authentication with Active Directory

**URL:** <https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942>\
**Category:** Pritunl VPN\
**Created:** [January 6, 2025, 7:15pm UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942 "2025-01-06T19:15:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Glenn](https://forum.pritunl.com/user_avatar/forum.pritunl.com/glenn/32/1149_2.png) [@Glenn](https://forum.pritunl.com/u/Glenn)\
**Post date:** [January 6, 2025, 7:15pm UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942/1 "2025-01-06T19:15:33Z")

</div>

Hello,

I would like to check what is missing to finalize the configuration between my Windows Server 2022 Standard instance, hosted on Oracle Cloud, and our Pritunl server, also on Oracle Cloud.

We have already validated the communication between the two servers (they are communicating via UDP and TCP).  
The Windows Server Radius service is configured and communicating with the Pritunl server.  
The test user we created in Active Directory (user “xuxa”) already appears in the Pritunl web console.  
Question: Should the Pritunl server automatically synchronize all users and groups from our Active Directory? Or should we do it manually for each user?

 ![Screenshot from 2025-01-06 14-57-55](https://forum-static.pritunl.com/original/2X/a/acf2dfd8073154da39f89baebb471b48b5a4b994.png)  
 ![Screenshot from 2025-01-06 14-58-48](https://forum-static.pritunl.com/original/2X/5/53b7ee14dcb0cfb16cf4854c72634315c043e022.png)

---

<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:** [January 6, 2025, 9:58pm UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942/2 "2025-01-06T21:58:42Z")

</div>

The user will login from the Pritunl web console with the Radius username and password. The Pritunl user is created on the first login.

---

<div class="post-metadata">

**Author:** ![Glenn](https://forum.pritunl.com/user_avatar/forum.pritunl.com/glenn/32/1149_2.png) [@Glenn](https://forum.pritunl.com/u/Glenn)\
**Post date:** [January 6, 2025, 10:38pm UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942/3 "2025-01-06T22:38:59Z")

</div>

But, it doesn’t connect with the AD user.

---

<div class="post-metadata">

**Author:** ![Glenn](https://forum.pritunl.com/user_avatar/forum.pritunl.com/glenn/32/1149_2.png) [@Glenn](https://forum.pritunl.com/u/Glenn)\
**Post date:** [January 6, 2025, 11:02pm UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942/4 "2025-01-06T23:02:00Z")

</div>

![image](https://forum-static.pritunl.com/original/2X/7/757701755b97ab03f4a40508379b0baabd611475.png)

Problem:

[summer-plateau-8340][2025-01-06 19:55:39,838][ERROR] Connection single sign-on not supported with current mode. Disable single sign-on authentication in server settings.  
sso\_mode = “radius”  
Traceback (most recent call last):  
File “/usr/lib/pritunl/usr/lib/python3.9/threading.py”, line 937, in \_bootstrap  
self.\_bootstrap\_inner()  
File “/usr/lib/pritunl/usr/lib/python3.9/threading.py”, line 980, in \_bootstrap\_inner  
self.run()  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/cheroot/workers/threadpool.py”, line 120, in run  
keep\_conn\_open = conn.communicate()  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/cheroot/server.py”, line 1287, in communicate  
req.respond()  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/cheroot/server.py”, line 1077, in respond  
self.server.gateway(self).respond()  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/cheroot/wsgi.py”, line 136, in respond  
response = self.req.server.wsgi\_app(self.env, self.start\_response)  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/flask/app.py”, line 2213, in **call**  
return self.wsgi\_app(environ, start\_response)  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/flask/app.py”, line 2190, in wsgi\_app  
response = self.full\_dispatch\_request()  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/flask/app.py”, line 1484, in full\_dispatch\_request  
rv = self.dispatch\_request()  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/flask/app.py”, line 1469, in dispatch\_request  
return self.ensure\_sync(self.view\_functions[rule.endpoint])(\*\*view\_args)  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/auth/app.py”, line 26, in \_wrapped  
return call(\*args, \*\*kwargs)  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/handlers/key.py”, line 1866, in key\_ovpn\_post  
return \_key\_request\_init(org.id, usr.id, svr.id, ‘ovpn’)  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/handlers/key.py”, line 1949, in \_key\_request\_init  
logger.error(  
File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/logger/ **init**.py”, line 55, in error  
kwargs[‘traceback’] = traceback.format\_stack()

---

<div class="post-metadata">

**Author:** ![Glenn](https://forum.pritunl.com/user_avatar/forum.pritunl.com/glenn/32/1149_2.png) [@Glenn](https://forum.pritunl.com/u/Glenn)\
**Post date:** [January 6, 2025, 11:03pm UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942/6 "2025-01-06T23:03:41Z")

</div>

![image](https://forum-static.pritunl.com/original/2X/2/21fe24a3465b59d9c509681bdff08bf7d27bb33c.png)

---

<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:** [January 7, 2025, 12:35am UTC](https://forum.pritunl.com/t/pritunl-authentication-with-active-directory/2942/7 "2025-01-07T00:35:16Z")

</div>

Radius doesn’t need [**single sign-on connection authentication**](https://docs.pritunl.com/docs/connection-authentication) it will authenticate directly in the client with the password prompt.

Disable the _single sign-on authentication_ in the server settings.
