Difference between revisions of "Authentication"

From the Linux and Unix Users Group at Virginia Teck Wiki
Jump to: navigation, search
(Account maintenance instructions)
Line 1: Line 1:
 +
= VTLUUG =
 +
 
VTLUUG uses [[Infrastructure:Chimera|chimera]] as it's FreeIPA server, and all VTLUUG hosts except [[Infrastructure:Joey|joey]], the router, are in its domain.
 
VTLUUG uses [[Infrastructure:Chimera|chimera]] as it's FreeIPA server, and all VTLUUG hosts except [[Infrastructure:Joey|joey]], the router, are in its domain.
  
Line 12: Line 14:
  
 
With the old deployment, [[Infrastructure:Acidburn|acidburn]] should be acceptable through normal password authentication over ssh. There is no need to configure tickets or anything else Kerberos related.
 
With the old deployment, [[Infrastructure:Acidburn|acidburn]] should be acceptable through normal password authentication over ssh. There is no need to configure tickets or anything else Kerberos related.
 +
 +
 +
= CAS =
  
  
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]

Revision as of 08:25, 3 January 2019

VTLUUG

VTLUUG uses chimera as it's FreeIPA server, and all VTLUUG hosts except joey, the router, are in its domain.

Account maintenance instructions

All users can log into Chimera's FreeIPA web GUI to edit their account. Yes, it does have a self signed cert. Get over it /s

For management of the entire domain, officers are able to add, remove, or modify users in any way.

History

VTLUUG has been was Kerberos and LDAP for authentication until the CVL eviction. We then migrated to an LDAP only domain due to a lack of IPv6 on behind router.ece.vt.edu. The old Kerberos server was configured to work on IPv6 only, therefore, we were required to migrate away from its use for authentication.

With the old deployment, acidburn should be acceptable through normal password authentication over ssh. There is no need to configure tickets or anything else Kerberos related.


CAS