Topics

@Rastin Mehr
Have created a new Topic
Please guide me
Thanks

I was thinking of adding a phone number and area code to the people_people table in the database but keep it optional. There will be no fields in the signup and account forms, but third-party developers can use the field for their own projects without having to make modifications to the core codebase.

Then you can develop some custom Anahita plugins to integrate with an external platform that sends a code via text message or push-notification and then you can use the code to authenticate the user.

Right now we don't want to add any new features to Anahita, especially if it requires building new user interfaces. That is until the React app is ready and we convert Anahita into an API-only service. Also, these external services don't pass the privacy compliance for scientific and healthcare projects that we do, so it is unlikely that we develop and maintain the code for it. You need to build authentication with a phone number on your own for now.

Did you have any particular service in mind?

Thanks for you reply,
At the moment thinking of Twilio OTP service.
we integrate this Service in our mobile app to verify the mobile number with OTP.
Then post the mobile number, username, email to the back-end .

once you add the mobile number to the database, can we use the mobile number as optional to sign in with API?

I can add the phone number and area code fields in the people_people table. You need to implement the Twilio integration plugins yourself. You can publish them on Github for others to use as well. I should be able to have the fields in one of the next two releases. I can't promise a time though.

Great, Twillo integration is on the client side. I will publish it once am i done.
can you please tell me where do we handle the validations for signup in the back-end?
for the moment i want to use the username field to allow only numbers , so i can use it as a mobile number for signing to the api.