Enable use of secure resources #53

[syedfkabir]

Resolves #53

Changes

• added <RequireLogin /> component to <KettingProvider />
• added a small onSuccess helper

Notes

Steps so far…

Made sure KettingProvider is encapsulating RequireLogin

Made sure RequireLogin encapsulates Routes

Could not use config found in storysuite
so I hard coded the token and authorizeEndpoints param
This wasn’t so difficult as the config just produced the a12nserver’s uri

Added a onSuccess that redirects the user to the home page ( ‘/‘ )

When hard coding the cliendId, I realized I needed to create the app in a12n get the clientId
Made tt-app in a12n
Made sure to add http://localhost:8902/ as a valid redirectUri (otherwise would not work by default)

The front end would give a ‘Not Authorized’ page when running an ‘authenticated backend’.
After implementing the steps above, I am no longer getting a ‘Not Authorized’ page
Instead I am getting the home page, or whatever page I was on.

this works, but I expected there to be a login process for the FE as well,
Just as there is one for the BE currently.
If I understand correctly, I may have reached the end of what I can do for this PR.
Currently there is no ‘access control’ in the TimeTracker,
I’m assuming I need to implement that before I get the login screen as expected on the FE.

[evert]

This all looks pretty good to me. I assume you tested this, and it works?

In a follow-up ticket we should move the a12n url and the tt-api urls into the environment, but that doesn't have to happen here

[evert]

2 last notes:

1. Instead of asking users to set up the redirect uri, provide a similar link the README.md just like we did for tt-api.
2. If you didn't get a login screen and immediately redirected back, you probably were simply already logged into a12nserver.

If 1 is resolved, this can merge! Good to have the tt-app merged before tt-api because it will still function even if the tt-api stuff isn't there yet.

[syedfkabir]

1. Instead of asking users to set up the redirect uri, provide a similar link the README.md just like we did for tt-api.

DONE!!

2. If you didn't get a login screen and immediately redirected back, you probably were simply already logged into a12nserver.

Yes! And if I wasn't logged into a12n or tt-api, I'd get a 'not authenticated' screen as expected.