feat(frontend): authorization frontend

[Mogge]

🍰 Pullrequest

Based on #403

Issues

• fixes 🚀 [Feature] Protect Frontend Routes #370

Todo

• None

[Elweyn]

Seems good but could not test it...

[Elweyn]

I can't let it run with docker but if I change presenter/server/index.ts to default port 3001 then I test it with:

• cd authentik && docker compose up
• cd frontend && npm run dev || prod
• cd presenter && npm run dev || prod

The logic works fine

[ulfgebhardt]

The guard throws serious errors - I am fine with merging this and resolve it after - but there is a problem.

[ulfgebhardt]

The page /signin contains the signout button. This button must be reactive to the logged in state and not visible when not logged in (can be postponed)

[ulfgebhardt]

I think we should require correct values for this - maybe we want so set a default here, since the frontend only makes sense to operate when authentication is possible.
Furthermore the default values for

 AUTHORITY: (import.meta.env.PUBLIC_ENV__AUTH__AUTHORITY ?? '') as string,
  AUTHORITY_SIGNUP_URI: (import.meta.env.PUBLIC_ENV__AUTH__AUTHORITY_SIGNUP_URI ?? '') as string,

make no sense anymore, since the presenter hides its buttons, not the frontend

Furthermore AUTHORITY_SIGNUP_URI is not needed in the frontend.

[ulfgebhardt]

I think we should require correct values for this - maybe we want so set a default here, since the frontend only makes sense to operate when authentication is possible. Furthermore the default values for

 AUTHORITY: (import.meta.env.PUBLIC_ENV__AUTH__AUTHORITY ?? '') as string,
  AUTHORITY_SIGNUP_URI: (import.meta.env.PUBLIC_ENV__AUTH__AUTHORITY_SIGNUP_URI ?? '') as string,

make no sense anymore, since the presenter hides its buttons, not the frontend

Furthermore AUTHORITY_SIGNUP_URI is not needed in the frontend.

Fixed - I kept the AUTHORITY_SIGNUP_URI since that would cripple the authService if not present.

[ulfgebhardt]

The page /signin contains the signout button. This button must be reactive to the logged in state and not visible when not logged in (can be postponed)

Fixed aswell

[ulfgebhardt]

Still doesn't work in production.

While I can see it working in dev, I don't get it to work on production.

Running on dev I can see the redirect happening on console and browser.

npm install
npm run dev

In production nothing happens neither on console nor in the the browser

npm install
npm build
npm run server:prod

[Mogge]

Looks like a build problem to me. The guard does not trigger at all all when building for production. If I remove all the code and just leave a console, no output is seen anywhere