Front end things to do

[rr-phillips]

• profile page
• get links working
• footer
• terms of service
• privacy policy
• add conditional to logged in users
• login btn changes to logout
• register btn goes away
• profile link gets added (not displayed until someone is logged in)
• my groups link gets added (not displayed until someone is logged in)

[tomqle]

I am trying to build the frontend's login behavior working (logging in removes the Login and Register buttons and shows Profile and Logout buttons instead). However, I am not sure how the authentication works with the current API. The below screenshot is from settings.py and it is commented out.

Was the plan to set up JWT authentication? I can go ahead and proceed with setting this up. Alternatively, we can also use DRF's TokenAuthentication which is simpler to set up but not as secure. That way we will be handle log ins and log outs. As far as I can tell, tokens are not being saved anywhere when a user logs in so it doesn't seem like any users can be authenticated at the moment.

[zrmeier]

Its been a while since I've touched it but i believe we are saving tokens. Its somewhere in the db i think but ill have to try and look this weekend. I have been really busy lately so I haven't had time to contribute as much as I had.

…

On Thu, Jun 17, 2021 at 11:31 PM tomqle ***@***.***> wrote: I am trying to build the frontend's login behavior working (logging in removes the Login and Register buttons and shows Profile and Logout buttons instead). However, I am not sure how the authentication works with the current API. The below screenshot is from settings.py and it is commented out. [image: image] <https://user-images.githubusercontent.com/6925373/122501092-e21def00-cfa8-11eb-85b1-54c742fdba5b.png> Was the plan to set up JWT authentication? I can go ahead and proceed with setting this up. Alternatively, we can also use DRF's TokenAuthentication which is simpler to set up but not as secure. That way we will be handle log ins and log outs. As far as I can tell, tokens are not being saved anywhere when a user logs in so it doesn't seem like any users can be authenticated at the moment. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVPHDUXCICOQKRBNQHKDOLTTK4ZJANCNFSM44N7QR7A> .

[zrmeier]

So I have a couple endpoints that set up at the following sites
After you activate the environment and get the server running here are the endpoints we have at the current moment:

• http://127.0.0.1:8000/api/v1/custom/register/

• http://127.0.0.1:8000/api/v1/custom/verify-email/ - Not Valid Yet

• http://127.0.0.1:8000/api/v1/custom/user/

• http://127.0.0.1:8000/api/v1/custom/login/

• http://127.0.0.1:8000/api/v1/custom/logout/

• http://127.0.0.1:8000/api/v1/custom/password/reset/ - Not Valid Yet

• http://127.0.0.1:8000/api/v1/custom/password/reset/confirm/ -Not Valid Yet

• http://127.0.0.1:8000/api/v1/custom/password/reset/change/

When you create a user you receive a token, but then you can also login. And I know its getting saved cause when I go to the

• http://127.0.0.1:8000/api/v1/custom/user/ it allows me to access the user info for the current user. Otherwise it will say you are not authenticated.