FAS Research Computing - Openauth/Two-Factor issues for new users – Hendelsesdetaljer

System under vedlikehold

Status page for the Harvard FAS Research Computing cluster and other resources.

Cluster Utilization (VPN and FASRC login required): Cannon | FASSE


Please scroll down to see details on any Incidents or maintenance notices.
Monthly maintenance occurs on the first Monday of the month (except holidays).

GETTING HELP
Documentation: https://docs.rc.fas.harvard.edu | Account Portal https://portal.rc.fas.harvard.edu
Email: rchelp@rc.fas.harvard.edu | Support Hours


The colors shown in the bars below were chosen to increase visibility for color-blind visitors.
For higher contrast, switch to light mode at the bottom of this page if the background is dark and colors are muted.

Openauth/Two-Factor issues for new users

Løst
Nedsatt ytelse
Begynte på 13 dager sidenVarte 2 dager

Påvirket

Authentication

Nedsatt ytelse fra 4:25 PM til 8:11 PM

Authentication

Nedsatt ytelse fra 4:25 PM til 8:11 PM

FASRC Two-Factor (OpenAuth)

Nedsatt ytelse fra 4:25 PM til 8:11 PM

Oppdateringer
  • Løst
    UTC
    Løst

    This issue is resolved and normal authentification for new accounts or accounts whose tokens have been reset/revoked can now log in.

    In the event that you find your token is not working still, we recommend you revoke your token and get a new one. See the last and first sections here, repectively: https://docs.rc.fas.harvard.edu/kb/openauth/

  • Oppdater
    UTC
    Oppdater

    If you have an existing 2FA token, please do not reset it at this time.

    We are continuing to work on a fix for this incident.

  • Identifisert
    UTC
    Identifisert

    We have identified an issue which keeps new accounts from using their two-factor/openauth token for authentication.

    This would also affect anyone resetting their token.

    If you have a new account and are unable to authenticate to the cluster, FASRC VPN, or other FASRC services, this is why.
    Existing accounts are not affected.

    We are working to resolve this as quickly as possible, but no ETA at this time. We will update this status as things change.


    Thanks for your understanding and patience.