Forward keycloak token in Authorization header in order to simulate JWT Forwarding in Cluster locally for development.
mwinberry/keycloak_proxy
Authorization is being handled in service mesh, with keycloak, for deployment and that service mesh forwards a jwt in the authorization header for example: Authorization: Bearer {token}. This application does not refresh the token as the expectation is that the service mesh is handling all authentication and security prior to any request being sent to the front end or back end.
Create docker compose file with both keycloak (which ingests your realm and client settings) and this application to ensure keycloak is up and running.
Use the /login url to initialize a user session with keycloak. This url will redirect you back to your front end application after successful authentication. Set your log out functionality in your front end to link to the auth logout url as env variable that can be changed in production to match your service mesh logout url.
Websockets have not yet been tested. The boiler plate for upgrading sockets is within the app. Users may want to add specific endpoints for your sockets. Sockets may default to xhr polling if using socket io and the connection is not upgraded. If sockets work please let me know, otherwise it is on the todo list.
Can be changed in ENV Variables.
GET proxy/home
GET proxy/login
GET proxy/logout
POST /setToken
Adjust as neccessary to prevent conflicts with backend endpoints.
These will be set in your docker file. Or .env for local execution.
Your keycloak auth url ends with /auth.
The url for your local keycloak instance.
Ensure keycloak is set to accept redirect urls from the running host port 8000.
The keycloak realm.
The keycloak Client Id
Font end url. Ensure all requests from front end are sent to this applications url at port 8000 in order for jwt to be added prior to the request being sent to backend. Suggest env variable in front end that can be changed for production containers.
The url for requests to be proxied to. Ensure this is replaced with your machine ip address if you are running this application in docker container and your back end is running locally outside of container.