Revisit and Revamp TOM Registration

[jchate6]

Goals:

1. Get tom_registration functional
2. Understand SNEX needs for transitioning from Snex1
3. Make sure tom_registration meets requirements to retire snex1

We need to bring TOM-Registration up to speed.
See

• Add support for OAuth to the TOM Toolkit tom_base#719
• Create an extended User Model tom_base#1051

Some steps along the upgrade path:

• manage dependencies with poetry #8
• use poetry_dynamic_versioning #9
• expose version to a context and template somewhere
• remove tom_registration_base from repo
• Add ability for a user to un-register
• simplify installation by using integration points #10
• Update ReadMe #11
• Get tests Working #13
• Get Tests Passing #14
• Add Registration Profile
• add page to generate new user accounts and list user accounts needing approval (SNEx2)
• Allow multiple affiliations
• Include Author List
• Request Latex name (BHTOM)
• Include ORCID (BHTOM)
• Support API Tokens
• Forgot Password option
• CILogon/alternative registration
• 2 factor Authentication
• add to tom_demo for demonstration and testing purposes

[jchate6]

From SNex2: Needs a page to generate new user accounts (and have us approve them)

[jchate6]

BHTOM Registration:
https://github.com/BHTOM-Team/bhtom_custom_registration/tree/eab3afd1272c2026033e99adb5e0d4fe91d954b5

[mpgh]

as a side-remark, for to be compliant with data protection, being able to de-register and rm personal data would be necessary. In principle, admin users can do this by contacting admin users, but I am not entirely sure if this is clear to all users registered to all TOMs.

[jchate6]

as a side-remark, for to be compliant with data protection, being able to de-register and rm personal data would be necessary. In principle, admin users can do this by contacting admin users, but I am not entirely sure if this is clear to all users registered to all TOMs.

Excellent point.

• Add ability to remove yourself from a TOM Toolkit tom_base#1103