DB accounts for use in production migration (pre-Shibboleth)

[eporter23]

In order to continue with production data migration in our project timeline, we want to add more accounts to our current authentication database so that we can run ingests and have them tied to a more recognizable human username until we have Shibboleth fully implemented.

For any accounts created, we should match them to actual Emory net ids, names, or email addresses, so that preservation events and Fedora and SOLR data show a real user instead of the dummy account names.

We should also investigate what will happen once we add the real Shibboleth accounts.

Initial steps (done through the UI):

• Add an account for Emily
• Add Emily to the Admin group

Investigations:

• Will we need to merge or reconcile these later to preserve deposit history, asset "ownership", etc?
• Will temporary accounts have to be deleted from our db once we move to Shibboleth?
• If we have to wipe out these accounts, is there a way can we still transfer permissions ownership to the new accounts?
• Is there a way we can test this in o24-test, using the new db account I created for myself?

[eporter23]

Notes from meeting with Collin and Torri: we think that we can retain db accounts in addition to Shibboleth accounts, so the risks noted above should not be a huge impact. We will ensure that users can only register with Shibboleth at the time of launch, however.