Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Servers:SAD-AUTH01: Difference between revisions

From sysadminafterdark docs
No edit summary
No edit summary
 
(12 intermediate revisions by the same user not shown)
Line 12: Line 12:
  |Hard Disks = 128GB, SAD-SAN01 (DS01)
  |Hard Disks = 128GB, SAD-SAN01 (DS01)
  |Disk Controller = VMware Paravirtual
  |Disk Controller = VMware Paravirtual
  |Network Adaptor= VMware VMXNET3
  |Network Adapter= VMware VMXNET3
  |IP Address= 10.1.30.7
  |IP Address= 10.1.30.7
  |VLAN = [[Network: ProductionFrontend30]]
  |VLAN = [[Network: ProductionFrontend30]]
Line 19: Line 19:
}}
}}
== History ==
== History ==
[[Servers:SAD-AUTH01]] was built on 5/10/22 to replace a pre-documentation server SAD-SSO01, which ran [https://goauthentik.io/ Authentik]. Authentik was a very good free and open source SSO solution that enabled internal users to authenticate to several internal services, such as [[Development:Gitlab]] on [[Servers:SAD-GIT01]]. However, MandolinSara and I decided it would be a good idea to get our multi-factor authentication services off premises in the event of an outage, a security threat, streamlined management and most important of all: easy two factor authentication for Windows and Linux servers. In addition, this enables us to protect certain consoles such as [[Disaster Recovery: VEEAM Backup & Replication]], [[Microsoft System Center: Microsoft System Center]], and [[Virtualization: VMware vCenter Server Appliance]].  
[[Servers:SAD-AUTH01]] was built on 5/10/22 to assist in [[Authentication: Microsoft NPS]] RADIUS authentication and run the [[Authentication: Microsoft Entra Cloud Sync]] agent.




For Duo's price point and added benefit, it was a no brainer to migrate things to a proprietary external service. If Authentik ever receives this functionality, a test server should be spun up to determine if the business should migrate back.
[[Authentication: Microsoft Entra Cloud Sync]] is running on this server to enable syncing between on-prem [[Authentication: Microsoft Active Directory]] and [[Authentication: Microsoft Entra Cloud Sync]], a component of [[Cloud: Microsoft Azure]].
 
 
Finally, the [[Authentication: Microsoft NPS]] server role is installed and setup to enable RADIUS authentication to [[Hardware: SAD-HME-FW01]] for [[Network: Road Warrior VPN]] to enable a secure connection back to sysadminafterdark networks.


== Purpose ==
== Purpose ==
The following roles and features are running on this server:


* [[Authentication: Microsoft Entra ID Connect]]
Windows Server Desktop was chosen because [[Authentication: Microsoft Entra ID Connect]] and [[Authentication: Microsoft NPS]] does not support Linux or Windows Server Core. It was easier to run these services from one device and have one point of authentication services in addition to [[Authentication: Microsoft Active Directory]]. The following roles and features are running on this server:


* [[Authentication: Cisco DUO Application Proxy]]
* [[Authentication: Microsoft Entra Cloud Sync]]
 
* [[Authentication: Microsoft NPS]]  


== Network Diagram ==
== Network Diagram ==
== Status ==
This server has been staged and placed into sysadminafterdark production. There are no plans to replace or upgrade this server until Windows Server 2022 goes end of life on October 14, 2031.

Latest revision as of 11:45, 2 July 2024

History

Servers:SAD-AUTH01 was built on 5/10/22 to assist in Authentication: Microsoft NPS RADIUS authentication and run the Authentication: Microsoft Entra Cloud Sync agent.


Authentication: Microsoft Entra Cloud Sync is running on this server to enable syncing between on-prem Authentication: Microsoft Active Directory and Authentication: Microsoft Entra Cloud Sync, a component of Cloud: Microsoft Azure.


Finally, the Authentication: Microsoft NPS server role is installed and setup to enable RADIUS authentication to Hardware: SAD-HME-FW01 for Network: Road Warrior VPN to enable a secure connection back to sysadminafterdark networks.

Purpose

Windows Server Desktop was chosen because Authentication: Microsoft Entra ID Connect and Authentication: Microsoft NPS does not support Linux or Windows Server Core. It was easier to run these services from one device and have one point of authentication services in addition to Authentication: Microsoft Active Directory. The following roles and features are running on this server:

Network Diagram

Status

This server has been staged and placed into sysadminafterdark production. There are no plans to replace or upgrade this server until Windows Server 2022 goes end of life on October 14, 2031.