I’m having trouble determining what is the best solution for me.
The reason I started looking into Auth0 is I wanted a way to store my user data without having to worry about writing all the scripts for encrypting the user data such as passwords. I wanted to use Auth0’s database store… but I’m beginning to think that it can’t provide me the user data that I need to store.
In the database, I need my users to have a username field, password field, and a second password. This second password you can think of as an access code (It can be the same for all users). This password will be sent to another API that will need it in order to handle sending messages for users.
My initial thought is that I could set a global password where I can call the API from the post-registration web hook to insert this password into their database… but then, I’m not sure how I can retreive this password from my mobile side code? My other issue is that each user MUST have a unique username that they cannot change. This username will be inserted into the API’s database.
My other issue is that I noticed Social Logins do not create a username field. =( A username field would be required because I need a field that will ALWAYS stay the same so that I could grab that data from Auth0’s database and send it to the other API’s database. And then when I need the information I still need to know what username was stored in the other API’s database for the user.
Anyone have any suggestions?
If I went with a custom database on Auth0, what are the disadvantages?? Would this still prevent me from offering social login… because I still need a unique username?? Is there a way to auto-generate a username field for ALL login types? Would I still have to figure out encryption if I used a custom database???