created: 2024-11-13 04:32 tags: - daily-notes

Wednesday, November 13, 2024

<< Timestamps/2024/11-November/2024-11-12-Tuesday|Yesterday | Timestamps/2024/11-November/2024-11-14-Thursday|Tomorrow >>

🎯 Goal

• [x] Resolve the password reset functionality issue.

🌟 Results

• Resolved the password reset functionality issue.

🌱 Next Time

• Update the password reset workflow to handle expired password verification links.

📝 Notes

Yesterday Sendgrid got back to me and said that my account was inactive which was causing my API calls to be received, but not used. I can see in the platform that the requests were made (and I can even see that the email appears to be formatted correctly) however I think a platform issue is preventing me from completing this task. I created a new account but was barred from logging in. At this point it may just be worth it to use a new service.

Also I found out that my main AWS bill is coming from a Virtual Private Cloud, specifically AWS VPC. Not sure if I'll still need to use this, but might be worth looking into when it comes to using a Virtual Private Cloud with the DIMMiN App instead of the HitHub App.

Anyways I was tired of waiting for Sendgrid to fix their shit. I decided to set up an account with Google Workspace using my custom dimmin.com Web Domain name.

After creating my Google Workspace account, I hooked it up to my DNS via a few different records. I created an app password associated with my Google Workspace account, then authorized the DIMMiN App to use that password to authorize sending via SMTP from the routing permissions.

Then, FINALLY, I was able to send a freakin email. It appeared in the "sent" portion of my Google Workspace email, then sure enough it appeared in my inbox with the proper link that allowed me to reset my DAMN PASSWORD!

At long long last (since June 2022) I now have basic user password reset functionality. YAYYYYY!

Only new issue is that when the user clicks the link after resetting the password they are taken to the following page

--redacted--

which should instead let them know that their password reset link has expired. Password reset flow works nicely, I just need to add a Django View, Django Template, and Django Route to handle expired verification links.

First I created the registration/password_reset_expired.html Django Template that let the user know that they needed a new link (and linked them to the password reset page via {% url 'password_reset' %}).

Turns out I was using a custom Django View to handle the entire user auth process. Django was implicitly handling certain routes for me which is why I didn't see them in my Accounts App Django Routes (urls.py) file. I'd instead like to explicitly define my Django Views for this process (and maybe update the sign up view as well).

I ran out of time this morning, but I'll work on finishing up the Accounts App / user auth tomorrow. For now I pushed changes to production and added my workspace credentials to the heroku config vars. Sure enough, it worked in Production. Nice.

Notes created today

List FROM "" WHERE file.cday = date("2024-11-13") SORT file.ctime asc

Notes last touched today

List FROM "" WHERE file.mday = date("2024-11-13") SORT file.mtime asc

(Template referenced from Dann Berg, can be found here)