Back
Similar todos
Load previous page…
Make cookies HttpOnly so other 3th party scripts can't access my customers' credentials (it was needed for websockets, but solved it without cookies) 
#simpleanalytics
experiment with non-sequential user/position IDs for confidentiality (github.com/ai/nanoid) 
#kornwolf
Strengthed online data security 
#chores
fix lets encrypt conf to work with my deployment
disable fetching user info from npm due to request errors 
#pkgstats
optimize authentication to persist anonymous data from new user 
#honesttribe
Set up console1984 to audit production data access and keep user credentials encrypted 
#auto
Figure out how to authenticate the Next.js app 
#auralite
Discover and fix webauthn-related security hole during testing. Now including a session ID with each request to prevent malicious users from mucking with other people's credentials 
#simpleotp
integrate nodejs bot for clients saas api - Auth 
#freelancegig
~~Add encryption for data~~ Use owner instead to access data if owner is set 
#quicklogging
CRA -> Next.js migration - simplify auth just use single token cookie remove refresh token 
#quizwhizzer
jwt nextjs Apollo 
#lab
Learn NodeJS Authentication - Passport.js
set up local 
#discountkit environment and begin debugging auth issues. I regret building this in express.js
v1.1: persistent user credentials through sessions 
#linefm
Spend all day debugging/researching auth cookies issue in Next.js 
#stronger
fix encryption problem