Added Authentication

[Corepex]

Changes in this pull request

Resolves #110
Related to pimcore/studio-backend-bundle#91

[Corepex]

Where / How to store the token?

• in the localstorage of the browser. CSP, Fingerprinting etc. will help us to protect the secrets

How will the token be refreshed?

• via setInterval - (lifetime - 80% = refresh) -> save deadline (in unix) to store on login/refresh

[Corepex]

Note:

This PR doesn't include the final security concept since it's not finalized yet.
It also doesn't include a refresh interval for the token.

Keep an eye on the follow-up PRs 💯 🍾

[vin0401]

I have to admit that the folder structure confuses me a bit and makes it hard to see how the things are connected.
My suggestion would be the following:

app/
  router/
    router.ts // <- takes care of the route handling. Maybe also offers the possibility to register routes early on before the are processed by the createBrowserRouter. 
   
components
   // if any presentational or purely UI components are available place them here.

modules/
  app/
    default-page.ts // new suffix -page to indicate a react component that is registered via module as a page.
  auth/
    login-page.ts
    // everything related to the auth module. Mostly the parts under componets/login-form
    // and also the auth-slice should go here. That way we can group all files based on the feature.

[vin0401]

Any updates due to the folder structure?
For me it still would make sense to group everything by feature in a new module called "auth": #237 (comment)

[sonarcloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud