How to Register Your CNDA2 Account
Overview
CNDA is migrating to a new system (CNDA2) that uses WashU Key for authentication instead of local usernames and passwords. All users must create a new CNDA2 account.
Before You Start
- You must have a WashU Key
- WashU faculty and staff already have one
- External users must apply for one — see How to Obtain a WashU Key
- You will create a new account on CNDA2
- Your existing project access will be re-linked once data migration is complete — we will announce when the system is ready
Step 1: Create Your CNDA2 Account
- Go to: https://cnda2.wustl.edu
Important
- Do not enter anything in the USER or PASSWORD fields
- Do not click Register or Forgot Login
- Click WUSTL Connect

- Log in with your WashU Key
- Complete two-factor authentication if prompted
Step 2: Complete Registration
After authenticating, you will be redirected back to the CNDA2 registration page.

- Ensure A New CNDA Account is selected
- Replace the generated username with your existing CNDA1 username
Username Requirement
You must enter the username you currently use on CNDA1. If you use a different username, your project access cannot be linked automatically. Your WashU Key is assigned an internal ID that only WashU IT can see — your CNDA1 username is the only identifier we have to connect your new account to your existing projects.
- Verify your first and last name are in the correct fields — some browsers autofill them in reverse order, as shown in the screenshot above. Correct manually if needed.
- Click Submit
Step 3: Wait for Migration Completion
After registering:
- Do not begin normal work in CNDA2 yet
- Wait for the official migration announcement
You will be notified when the system is ready for use. Your project access will be restored automatically at that time — no action is needed on your part.
Notes
- Your old CNDA account is not transferred automatically
- Project access will be re-linked automatically based on your CNDA1 username on the cutover date — no need to contact the Help Desk
- Scripts and XNAT Desktop Client users will need alias tokens after cutover — see How to Generate and Use Alias Tokens
