@rp, We have created an API get_user_details, whic...
# support-questions-legacyn
namanchhabra_60978
09/28/2023, 8:12 AM@rp, We have created an API get_user_details, which gives us the details of the currently logged in user from the session object. But, we noticed, if the user's email is not verified and if the email verification is marked as 'REQUIRED', the API gives an 500 error whereas, if it is marked as Optional, it works.
What could be the possible reason of the failure of the API, if the email is not verified? As the user is logged in, shouldn't the session object exist?
r
rp_st
09/28/2023, 8:14 AMhey @namanchhabra_60978 have you added our middleware to the python backend? It should not give u a 500, but give you a 403
rp_st
09/28/2023, 8:14 AMwhats the error stack?
n
namanchhabra_60978
09/28/2023, 8:15 AMI'm so sorry, yes it was a 403 error
namanchhabra_60978
09/28/2023, 8:15 AMAnd yes I have added the middleware to the python backend and everything else is working fine
namanchhabra_60978
09/28/2023, 8:15 AMOnly this issue we are facing
r
rp_st
09/28/2023, 8:15 AMright
rp_st
09/28/2023, 8:16 AMso the user has to go through the email verification flow
rp_st
09/28/2023, 8:16 AMand verify their email. Only then will the api access be given,
rp_st
09/28/2023, 8:16 AMsince it's in required mode.
n
namanchhabra_60978
09/28/2023, 8:55 AMActually, we wanted to show 2 different email verification screens: different for both email password auth and SSO. So, we needed the parameter that has the user logged in via thirdparty or not.. So we were trying to achieve this
namanchhabra_60978
09/28/2023, 8:55 AMAny other way to do so?
r
rp_st
09/28/2023, 8:56 AMyea that is possible. In the session's access token, you can add if the user is email password or not, and then read that on the frontend, and then decide which screen to take the user to
n
namanchhabra_60978
09/28/2023, 9:06 AMcool! Thanks a lot @rp_st
2 Views