GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
- Pending memberships are saved into the main members table
- Account is created in AD/dispense using provided details
- Update dispense with payment information after account creation - transfer money from `uccportal` account to `$newuser` account (for example)
- User gets email with link to login & change details
4. New member gets notification (ie. email), clicks link to set password
- __Use case 2: existing member__ (possibly with locked account):
1. Existing member (with existing AD/LDAP account) logs in and enters details on renewal/registration form (or confirms existing stored details are correct)
...
...
@@ -51,6 +52,7 @@ Environment Setup
-`cd uccportal`
-`virtualenv env`
- Every time you want to do some uccportal development, do `source env/bin/activate` to set up your environment
- Install packages needed by pip to build python dependencies: `apt-get install build-essential libldap2-dev libsasl2-dev`
- Install python dependencies to local environment: `pip install -r pip-packages.txt`