Clarify backend environment variables and routes

[jasalisbury]

This is a tech debt/technical ticket.

#4 enabled users to login and logout of the TTA Smart Hub. In this ticket a new environment variable was added, TTA_SMART_HUB_URI. My plan was for this variable to eventually replace REDIRECT_URI_HOST since they are the same value in most cases. The only place they are not the same is in local development. I thought we were going to be able to update the HSES callback to localhost:3000... but it has to stay localhost:8080..., which throws a wrench in my plan.

#4 also prepended api routes with /api. It would be nice if we can update our HSES callbacks to include /api in their paths to simplify the backend code.

We need to take some time to think about the environment variables and how we can change the HSES callback. Some options to start thinking about:

• Swap the ports on the backend (currently 8080) and frontend (currently 3000) and remove the REDIRECT_URI_HOST environment variable
• Keep both the REDIRECT_URI_HOST and TTA_SMART_HUB_URI variables
• Something else I haven't thought of

Questions

Can we update the HSES callback adding api (and potentially v1) to the path? I.E. http://localhost:8080/api/v1/oauth2-client/login/oauth2/code/

Acceptance Criteria

• All TODOs that deal with REDIRECT_URI_HOST are removed from the backend
• It is clear what each environment variable is doing with as little overlap as possible
• If possible, all API routes on the backend use the same router

[pamlo412]

Per discussion at standup grooming, @jasalisbury wants to review/update this issue before we groom and prioritize it.

[jasalisbury]

After reading this ticket after standup yesterday I think it is good to discuss as is.