Skip to content

refactor(go-website): Implement auth & triage page - #5842

Open
michaelkedar wants to merge 2 commits into
weblinterfrom
auth-shmauth
Open

refactor(go-website): Implement auth & triage page#5842
michaelkedar wants to merge 2 commits into
weblinterfrom
auth-shmauth

Conversation

@michaelkedar

@michaelkedar michaelkedar commented Aug 17, 2026

Copy link
Copy Markdown
Member

Implemented the google login page & cookies & connections needed for the triage page.

Auth stuff implements AES-256-GCM (instead of Flask's unencrypted signed cookies) to store the auth session client-side. I was thinking of using scs, but that is server side (would need to connect to redis), and I'd rather keep it similar to Flask's client-side stuff.


Stack created with GitHub Stacks CLIGive Feedback 💬

@michaelkedar

Copy link
Copy Markdown
Member Author

@jess-lowe can you make sure the Go triage tool still does what you need it to do

@jess-lowe jess-lowe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still does the thing 👍🏻

Comment thread go/internal/website/server.go Fixed
@michaelkedar
michaelkedar force-pushed the auth-shmauth branch 2 times, most recently from 2c30b3d to 59d22c1 Compare August 25, 2026 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants