You are browsing a read-only backup copy of Wikitech. The primary site can be found at wikitech.wikimedia.org

Difference between revisions of "CAS-SSO"

From Wikitech-static
Jump to navigation Jump to search
imported>Muehlenhoff
imported>Muehlenhoff
Line 12: Line 12:
  
 
* https://cas-icinga.wikimedia.org
 
* https://cas-icinga.wikimedia.org
* https://puppetboard.wikimedia.org (cas-puppetboard.wikimedia.org was a thing in the past, but will soon vanish)
+
* https://puppetboard.wikimedia.org
* https://cas-graphite.wikimedia.org
+
* https://graphite.wikimedia.org (cas-graphite.wikimedia.org was a thing in the past, but will vanish soon)
 
* https://tendril.wikimedia.org
 
* https://tendril.wikimedia.org
 
* https://people.wikimedia.org/~cdanis/sremap/
 
* https://people.wikimedia.org/~cdanis/sremap/

Revision as of 10:34, 8 July 2020

Our Web SSO infrastructure is built on Apereo CAS

When logging into a CAS-enabled website without an active SSO session you'll be redirected to the CAS login page (https://idp.wikimedia.org/login) The CAS service collects LDAP group memberships and makes them available to services for making authorisation choices. After authentication the users get redirected to the initiating service.

The authentication happens with your Wikimedia Developer Account name and the respective password. There's also be possibility to add a second factor using U2F, see below how to enable it.

If you select "Remember Me" during, a long term session is initiated. It lasts for seven days (or until you logout via https://idp.wikimedia.org/logout). Do only use this when working from a machine only used by yourself. If that's not the case and "Remember Me" is not used, your SSO session will expire after one hour of inactivity.

The current SSO setup is targeted at SRE staff (both to collect more feedback and painpoints before a wider rollout and also because there can still be disruptive changes which we don't want to impose on less technical users. That's why a number of services with a significant amount of non-SRE users are currently only enabled via a separate Apache site (to not interfere with users authenticating against plain LDAP).

Which services are currently enabled?

Enabling U2F as a second factor

Apereo CAS supports U2F as a second factor. This is configured on a per-user opt in basis and configured via LDAP. Supported browsers are Chrome/Chromium, Firefox (ESR68 and later, ESR60 had some issues in tests, but it's EOLed anyway now) and Safari (13 and later).

All Yubikeys issued by OIT should be compatible. Onlykeys were also reported to work (https://phabricator.wikimedia.org/T242438)

Requesting to enable U2F (if you're not in SRE)

Mid-term, enabling U2F for web SSO will be part of our account management. Until then, please open a task in Phabricator and apply the LDAP-Access-Requests tag. Your SSO account will be U2F-enabled by the SRE person currently on SRE Clinic Duty.

Enabling U2F for an account

To enable U2F as a second factor, run the following on mwmaint1002.eqiad.wmnet:

sudo modify-mfa --enable UID

To disable U2F, use

sudo modify-mfa --disable UID

UID is your shell username here (as that's what identifies your identity on the LDAP level), not the Wikimedia Developer Name). Once it's enabled, the next time you login, your token will be registered (Mid-term we'll have a proper identity management solution which will make registration on the shell obsolete. Note that CAS operates on the readonly LDAP replicas, so it might take up to two minutes minutes until the LDAP change is affective.

Known issues / FAQ