Set your custom backend URL from the app.

[josancamon19]

No description provided.

[josancamon19]

1. Requires new authentication method, so will set-up sign up/sign in pages, if the user sets a custom backend URL
2. modify the backend auth logic too, to handle this email/pwd in header
3. Prob still use firebase auth as source of truth.

Fuck, prob wouldn't still work, very complex.
Firebase doesn't allow to download the credentials files on the go, does it?

[beastoin]

haha yes, you got it bro.

[josancamon19]

• Authentication must be email/password

• Sign up / sign in backend endpoints

• Auth middleware on back should be able to handle email/pwd prob using jwt but /token and /refresh endpoints, manually generating the jwt

• App must have sign in / sign up forms

• on default sign in page, option to custom backend URL, once is set, local pref must be stored, and the alternative sign in sign up page must be shown instead of google or apple

• on auth, http requests must be done using this email/pwd jwt token generated.

• Clear instructions.

[josancamon19]

On the back will still use signInWithPassword shit

[beastoin]

bruh, do you think it's super important to have ? because rn i don't think so, sry :{

[mdmohsin7]

[ ] Authentication must be email/password

I think we can still use sign in with google / apple even if we move auth to the backend. Sign in with google/apple will generate only claims that are validated on the backend I guess

[beastoin]

my expectation is when this ticket done we could help the backend dev onboarding faster.

sry i dont think the end user would use this feature to link Omi mobile app with their backend - mainly because they would not willing/don't have the ability to host the backend them self.

now, the app dev could build the app with 01 command line setup.sh, the complexity of building the app have been reduced af.

then my assumption is, the backend dev's journey would be:
1/ build the backend themself, they dont need to build the app.
2/ if they need to test their backend with the app, they would:

• build the app - setup.sh to see how's it work with omi dev backend (~2 hours)
• try to replicate it with their backend (30' with the setup.sh + Omi doc)

that's why...

because rn i don't think so, sry :{

[josancamon19]

It would not be for existing users, it'd be to test a possible target user that actually works, I'm moving back to no status anyways.