[calsify] Fwd: Second Reminder: Action required: Update to IETF Datatracker password requirements starting 8 July

[Bron Gondwana <[e-mail]>]

Just in case any of you aren't on the announce list.

Don't wait until the start of the session and try to log into Datatracker to discover you can't get in and have to do a recovery, log into Datatracker this week and make sure it's still working for you!

Bron.

----- Original message -----
From: Robert Sparks <[e-mail]>
To: [e-mail]
Subject: Second Reminder: Action required: Update to IETF Datatracker password requirements starting 8 July
Date: Monday, July 14, 2025 11:16

If you have not already done so, please confirm that your password meets the new requirements as soon as possible.

NOTE: Please make sure the working password is set for both _datatracker.ietf.org_ and _auth.ietf.org_ domains. auth.ietf.org uses datatracker credentials. Sign-in to MeetEcho or any other service that uses datatracker credentials will use auth.ietf.org. You can test whether your password is properly set for auth.ietf.org by logging into _notes.ietf.org_.

Robert Sparks



On 7/1/25 2:59 PM, Robert Sparks wrote:
> Beginning with a Datatracker update scheduled for 8 July, after the I-D submission deadline for IETF 123 Madrid has passed, passwords for the IETF Datatracker will be required to have at least 12 characters and be sufficiently complex.[1]
> 
> You should verify your password meets the new requirements using the “New password” field on the change password form after logging in:
> 
> _https://datatracker.ietf.org/accounts/password/_
> 
> On that form, a complexity bar and text below the new password field will provide guidance. When the bar is green, the password will be accepted. If your current password does not meet the requirements, please go through the password change process to set a new one that does meet them. If you are not already logged into Datatracker, this process requires confirmation via your primary Datatracker email address.
> 
> IMPORTANT: If you are already logged into the Datatracker, do not assume that your password will continue to work without verifying it.
> 
> Especially if you plan to participate in IETF 123, you should verify your password meets these requirements as soon as possible. Datatracker login is required to join MeetEcho for meeting sessions, whether you are participating in-person or remotely. Logging into the Datatracker well before the meeting starts will help ensure you don’t encounter delays when joining a meeting session for the first time.
> 
> If you are the chair of an IETF working group or IRTF research group, please share this update with your group.
> 
> This change eases a future migration to an authentication system that will allow for federated login, MFA, and passkeys. The new system also will allow the authentication process used for various IETF-provided services to be more robust.
> 
> Another reminder about this change will be sent shortly after the Datatracker update is deployed on 8 July.
> 
> Robert Sparks Senior Director of Information Technology for the IETF LLC
> 
> [1] zxcvbn is being used to determine complexity (_https://github.com/dropbox/zxcvbn_)
> 
_______________________________________________
IETF-Announce mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]


--
  Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC
  [e-mail]