Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can use a random numerical ID as PK and let people associate as many authn IDs as they want after logging in with one.




Who in this scenario outlines the key infrastructure, and how is the private key maintained?


Why would you allow this complexity for basically nothing?

Using a separate table for authn is a basic pattern for this problem. What would you do?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: