Great tutorial. Have a question regarding how would i protect a backend api with this? For instance the frontend already has the access token but the api is of a different system that is not public.
There is a problem. If you put the token in the frontend, it will go to the user's machine and the backend will not be protected anymore as you exposed your keys. So static tokens, and basic auth will not work here. Maybe if you use an OAuth based approach, like with Github, that's better. At least those tokens expire and are linked to your identity. What you need to check is what cookie the auth parameters are stored in. If you are lucky you can access those cookies and you can send those tokens when you request the backend with your frontend. But chances are there is a browser sandbox limitation, and you won't be able to access the cookie.
You are right, the sound level is way too low. I was using a condenser mic which I was never able to set up properly. Either picked up every noise from the whole house or it was too quiet. I picked up a podcaster mic since then. Hoping to produce better sound levels in the coming videos.
These are the keycloak configs: oauth2-proxy.github.io/oauth2-proxy/docs/configuration/oauth_provider#keycloak-auth-provider You have to edit the manifests/oauth2-proxy.yaml manually, to match the config from the link above. Gimlet Stack will preserve your changes in future updates.
