Also I saw this and if this answer still true (no Basic auth support from the auth0) Custom sms provider then I guess it’s not possible to do using custom sms provider. Is there any suggestions or options?
Personal recommendation: After using more then 2 years I can say that it’s not worth to use Auth0 as a authentication provider, it’s better to spent bit more time and use your frameworks library. Over time you will have lot’s of headaches and less control with auth0.
As a solution this worked for me:
I used connection api to proxy sign in code to my backend and then manually sending that code to the users phone number using twilio verify api.
after this every time someone sign-ins your backend will receive POST request from auth0 which contains sms text inside json body, ex. “Your AppName verification code is: 1234”, you can extract code from the text and send it using twilio verify api or other sms service.
Thanks. This helps alot. I’ve been feeling the same way about whether to continue using auth 0 or not given its only been headaches since implementing.