More actions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
|Hostname = SAD-AUTH01 | |Hostname = SAD-AUTH01 | ||
|Type = VMware Virtual Machine | |Type = VMware Virtual Machine | ||
|Site | |Site = [[Site:HME]] | ||
|Rack | |Rack = [[Rack: HME-R01]] | ||
|Role = Authentication | |Role = Authentication | ||
|OS = Windows Server 2022 Standard Desktop | |OS = Windows Server 2022 Standard Desktop | ||
Revision as of 22:31, 12 May 2024
History
Servers:SAD-AUTH01 was built on 5/10/22 to replace a pre-documentation server SAD-SSO01, which ran 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.
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.
Purpose
The following roles and features are running on this server: