joshlong
commented
1 month ago also, use profiles should have images and such. could we get that from Auth0? a profile photo? one problem i was having was that the gateway, which is our client, wasnt transmitting much information to the resource server, where we actually initialize the user in the system. ive fixed this by reaching out directly to the usrinfo endpoint directly with the token in the mogul-service.
when the user first gets redirected to our app from Auth0, we know there's no existing user by that name, so we could write a flag saying whether or not the
mogul's been authenticated before. if not, it's in need of being onboarded. the client could detect this and show a form before the user gets a chance to use the system. initialize it with their username (which is immutable) and show a first name, last name, phone number, and email field.is there a way to do a validation email to confirm the user is who they say they are?
having email will let us eventually reconcile the various accounts when auth0 eventually gives us a way to read the email. maybe at the gateway? no idea, tbh.
what could we do to make the Ui sort of disable everything else and force the user into a sort of modal wizard that never relents until those fields are sourced?
we need the phone no. and email as a way to communicate with the user. we also need it as second factors. we need the name so as to show you something besides
hello gituhb | 2e24e2. Ideally, it'd sayhello, Josh.are there services we can use to establish the phone number is valid? maybe this is a job for ai? right now, collect eveyrthing as is. no fuss. emails can be validated of course.