MIT users are being directed to different institutions

[bofstein]

MIT admins are reporting that @mit.edu emails are being directed to the wrong university. By default they are put into Whitehead Biomedical institute, and if they go to select MIT, they are given many options.

MIT's ROR page has a website of web.mit.edu, with a domain listed as mit.edu.

We want to do the following tasks:

• Merge all the MIT institutions into a single organization, and move all existing users into the same, managed org.
• • They would probably prefer (mit.edu) as the domain in the name, but I think we should have it be (web.mit.edu), because otherwise I believe we'll always have a duplicate option in the list since that's what ROR will return.
• • I can do this in the UI if you let me know to, but I want to wait until any other changes are decided on.
• Adjust the sign-up logic so that @mit.edu emails default to this institution rather than Whitehead.

I do not think we should move Whitehead users over as we can't verify who is actually from there vs was incorrectly defaulted there.

[bofstein]

@briri the priority is high on this (i.e. by end of tomorrow if you can) just to do an initial check on what we need to fix this so I can respond to the user with a timeframe, but I'm fine with the fix waiting until the new year if it needs a code change or will take a while.

[briri]

Ok, we will need to do the following:

• Update 190 with name 'Massachusetts Institute of Technology (mit.edu)' to 'Massachusetts Institute of Technology (web.mit.edu)'. This is the one attached to the current ROR record
• Merge 7469 'Massachusetts Institute of Technology' into above
• Merge 13678 'Massachusetts Institute of Technology (mit)' into above
• Update code so that any user whose email ends with web.mit.edu and mit.edu to be directed to 190 so they get SSO button

[briri]

@bofstein i have run the DB scripts so there is only one MIT now.

I had to manually adjust the homepage we get from ROR for the Whitehead Institute and Koch Institute so that the email addresses for @mit.edu go to the correct SSO org.

The problem is that we will sync the ROR record on the 1st and reset those 2 org's homepages. I can login though and rerun the SQL scripts to set them back though.

I think there is very low risk since it only effects people creating an account, but between midnight on the 1st and the time I run the script, there could be a user trying to create an account that gets the Whitehead Institute instead of the MIT SSO button.

Once we're officially back, we can add the code change and this will not be an issue going forward after that.

# Run these on Jan 2nd
update registry_orgs set home_page = 'https://win.mit.edu' where id = 3395;
update registry_orgs set home_page = 'https://kin.mit.edu' where id = 107553;

# Run after code fix is in place to set the homepages back
update registry_orgs set home_page = 'https://wi.mit.edu' where id = 3395;
update registry_orgs set home_page = 'https://ki.mit.edu' where id = 107553;

[bofstein]

The problem is that we will sync the ROR record on the 1st and reset those 2 org's homepages.

Do we have the option to delay January's sync so that it doesn't happen until we're back and we can run the script then?

[briri]

not without releasing puppet environment changes.

[bofstein]

Ok, worth an ask. That plan sounds good, I agree its low risk to let it be off for sign-up for a couple days over break. I let them know that we implemented a temporary fix that might revert over break, and we'll do a full fix in January.