cch5ng / job_tracker

1 stars 0 forks source link

heroku redirect uri #85

Open cch5ng opened 3 years ago

cch5ng commented 3 years ago

after try to login, seems like there is an issue with the redirect uri (auth0-provider-with-history)

try logging out and see if the login flow seems to work otherwise

double check routes (which are accessible if logged in vs logged out)

cch5ng commented 3 years ago

check if it is an auth0 config issue or a google config issue

cch5ng commented 3 years ago

error currently seems related to audience configuration and api registration on auth0 settings; not sure if this is going to require refactoring the api, not sure how it is verifying auth status currently

resc

https://auth0.com/docs/get-started/set-up-apis

cch5ng commented 3 years ago

start from scratch on auth0 for dev, (new tenant, new FE app, new API config)

after that tests out successfully, replicate config pattern on heroku (verify that the api auth side works)

cch5ng commented 3 years ago

auth0 audience seems to be set incorrectly (should point to the client rather than the server ?)

X-(fixed) cur dev error

Error!Payload validation error: 'Object didn't pass validation for format absolute-https-uri-or-empty: https://localhost:3001' on property initiate_login_uri (Initiate login uri, must be https).

resc

https://community.auth0.com/t/application-login-uri-field-payload-validation-error-for-https-localhost-3000-authorize/31554/19

cch5ng commented 3 years ago

at end of auth flow (new user signup)

see post 401 error /oath/token

also verify should I be using auth0 provider with history ?

check importance of Token Endpoint Authentication Method from the application settings

todo, setup auth for the api

cch5ng commented 3 years ago

091721 > seems like missing bit is getting token from the client side and passing that to the server with api request

consider switching auth to firebase because seems like the documentation is not providing enough info on auth0

cch5ng commented 2 years ago

not merged but last changes for auth0 authentication

unable to resolve some inconsistencies where using both react app for auth and wanting to use auth for the BE api; unclear if they need to have different tenants