auth0-lock <v11 deprecation

[matthewberryman]

Now strictly unavailable as of two days ago:
https://auth0.com/docs/migrations/guides/legacy-lock-api-deprecation

[matthewberryman]

To-do:

1. Landing message "Silakan login untuk mengakses peta" no longer appears. Users can still log in using menu and this has been communicated to field office, although see menu disappears on small screen widths #40
2. Double check and make sure the UI complies with Auth0's rules for free open source projects.
3. Apply for free open source plan for petabencana-dev tenant.
4. Set up custom domain (under tenant settings -> add domain -> set up CNAME record in route53 -> -> drink coffee -> use auth0-managed certificate -> finish drinking coffee -> click on verify -> wait another 5-10 minutes (another coffee? :)). Update

   cognicity-rem/aurelia_project/environments/dev.js

   Line 6 in eec9c61

   AUTH0_DOMAIN: 'auth.petabencana.id',

   
   Note I would suggest auth-dev.petabencana.id as the domain.
5. Manually trigger build in jenkins (not auto triggering for some reason and not a lot of point to fix as we'll move to codepipeline + codebuild for PB soon).

[matthewberryman]

^^

• sorry but I saw and then lost link re open source plan details, and couldn't find it again (super exhausted here).
• I was hoping to hack it a bit and use custom domain from other tenant with CORS set up on both but got some 400 and 500 errors still.

[matthewberryman]

Badges: https://auth0.github.io/auth0-oss-badges/
Once that's done I can contact the OSS team via the link on https://auth0.com/pricing and then when that's done I can complete other steps.

[tomasholderness]

Badge added to landing page in: 01e81eb

Note that this won't show because the Auth0 script (https://cdn.auth0.com/js/lock/11.7.2/lock.min.js) is returning 400 errors and I think Aurelia stops page rendering.

[matthewberryman]

@talltom Thanks for doing this. It shows up on page load which is fine for now (and for good measure I will merge back to master to check on prod). I have applied for OSS plan for petabencana-dev and will keep you posted.

[matthewberryman]

Scratch that, I can see in #41 that there a bunch of other diffs as well, which seem moot in light of recent discussions (?), so for now I will cherry-pick the badge commit back in to master.