its simply my own (probably insecure) authentication server :]. provides login via otp, password and 2fa, plus can act as an OAuth2(.1) provider. it even has a frontend, oh my! :3
No followers yet
Once you ship this you can't edit the description of the project, but you'll be able to add more devlogs and re-ship it as you add new features!
i forgot to add the 2fa settings on the settings page lol. also fixed the beepauth logo not showing up on emails
haha, finally i finished this thing wahoo. the settings page of the frontend even fits on my phone, that means that the frontend is responsive i guess. oh, and it even has dialogs. pretty dilaogs in my birb opinion. as a final word before i click the glorious ship button, i a small birb, am proud of this projecto and i shall ship it before i break something again. i shall lie on my bed and sleep for 3h in peace for once
started making the settings part of the server thingy settings thinggy. it works and its simple and lacks features. i still have to make the authorized apps and my oauth apps pages. but eh, progress is progress even if it took me a while to make it work. i love wasting time
hell yeah, finally figured out the docker compose file and the little tiny fixes needed to be able to host my backend on nest. after going through the painful setup and stupid goofy mistakes that took me too long to catch, i must say that i no longer like docker
Finally fixed my wonky readme that fell short explaining how to even setup a dev environment for this badly put together thing. And also added a Dockerfile to be able to publish a package for the server for use in nest (its for the demo!!!!1)
Added the OAuth prompt and fixed a stupid error that I introduced when I reworked the handler plus one more that I think that existed before i reworked it. i also added the typical helmet like npm package response headers. looks clean i guess (i tried my best lol)
Cleaned up some pages on the svelte side while also reworking a little bit how I handle the OAuth2 authorizations so it's easier to handle on the frontend. Plus, fixed some really really dumb mistakes that I just catched on my backend lol. the only thing left is making the oauth prompt page on the svelte side and and everythings done for shipping wahoo
i love procrastinating. I added the reset password flow pages to the frontend with all the stuff it needs. wow
just started to hash the OTP codes with argon2. It is overkill as heck but oh well sure it's better than just storing them plainly inside the redis kv.
After trying to figure out how to make the password register flow work, I just decided to strip it out and only let you set a password after logging in via otp. The old register flow did work, but you could create a thousand accounts with random unverified emails that would all get stored in my db. I could have added a background job to clean up the unverified accounts or even ratelimitting but meh. one of the things I tried was to just add the account details into redis temporarily to then get an id to be used for the email verification to then create the user on the db. it is simple, but probably my implementation had the problem where a user could open two tabs or more and verify their email in one of those, making me have track their signup attempts or sessions to be able to delete them when they finalize one of those and blah blah more stupid problems. sooo, that means I will only rely on the modern otp login to let the user add the password they want because its simpler that way lol
hi there. 2fa login is also working now. I had to redo the error that was thrown when a 2fa challenge was required because before I was just returning an OK that could be the session info or the totp challenge. for some reason i couldn't figure out how to use that with the openapi-fetch because it only shown the session info schema and not the totp challenge one. so instead of that, i just return a 403 error which is pretty fitting for a totp challenge and easier to handle
finally got the login flow working. it should have been an easy job but, I wanted it to look at least pretty and functional. and to make it look pretty you gotta do a lot of revisions or something like that
spent like 5 hours doing nothing. all that time was spent on getting validation to spit out my error format and figuring out why the openapi schema wasn't picking up two of my enums. it was all so I could use the openapi-fetch library on the frontend. if you've got an openapi schema, you might as well use it, right? the fixes were so simple, which is just sad.
I'm practically going in blind with the frontend design but at least i think the login and register pages look great. I still have to do all the actual interactions and stuff but at least i have a design i can follow now :)
I was thinking about just shipping the project as it is. Just an API. But really, who the hell is going to write their own frontend on top of my API? I sure wouldn't lol. Sooo, i'll just build the frontend in svelte (stepping out of nextjs wahooo) before shipping. its going to be fun i guess
I just cleaned up the swagger api docs with nicer descriptions and added the responses that an endpoint can throw because before it was just a copy paste of the first endpoint I made lol
i just removed the old placeholder account recovery flows and replaced them with just one flow. it's the password reset one (woohoo), it pretty much just adds a new password to the account and deletes all sessions and does the typical checks and stuff. I still need to clean up the openapi descriptions and summaries tho
I tried making the existing oauth2 stuff compliant with the proposed oauth 2.1. it wasn't that hard lol, just had to harden the requirements. I've also added emails, like actual emails that aren't only text. and i did some backend work, creating and organizing endpoints and stuff to make it more complete... and added swagger (openapi schema) and a sudo mode like in github that might have a thousand bugs. probably
got oauth working with the ability to create new apps and stuff that oauth2 providers do. pretty cool right? It was hard as heck as I had to redo it like 4 different times for reasons like i don't like how it looks or its too messy or I planned for this and it will work as I wanted... oh crap it does not work as I thought... And I still don't like how it looks :(. BUT now's the right time to start cleaning up the code and adding stuff that i considered too early to add like real email templates and more endpoints to do stuff i guess
It took a big minute, but 2FA is basically implemented and working. That even includes recovery methods for the otp and totp (2fa) and all the extra email messages every service sends (like the new login or recovery codes used). And now only thing separating this from an auth server is oauth... so that's what I'm going to try and do next haha
Finished the password and otp login parts, plus session management. And I've added the settings file to not have everything hardcoded. the only things currently left are a needed refactor, and figure out how to add 2FA on these two thingys as I didn't even plan for it lol
Simple user register logic in place. plus some other stuff that make it work as intended. I still need to make settings for each stuff and actually implement the basic login/register via password.