-
I'm trying to hook up Spring Security to use a basic Authentik setup. Authentik is running in Docker via Docker Compose, as is my Spring Boot service. FYI, I've replaced the name of my application with {name} in my question; its not actually {name} in my config. I've tried the following roots for the URIs in my application.yaml file:
Authentik is running on port 80/443. It has the vanilla self-signed cert. If I go to the following URL in a browser, I get the JSON response as expected: http://localhost/application/o/{name}/.well-known/openid-configuration I can't for the life of me figure out why I can't get Spring Security to talk to Authentik on startup. I've been at this for days. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
My Spring Security config from my latest attempt, after having removed the 80/443 override from
|
Beta Was this translation helpful? Give feedback.
-
Found the solution. No modification necessary to the Authentik docker compose file. Modification was necessary for my app's docker compose file, however. I had to add the Authentik network to my app's container, and add this at the bottom:
Name of the network was ascertained by doing a |
Beta Was this translation helpful? Give feedback.
Found the solution. No modification necessary to the Authentik docker compose file. Modification was necessary for my app's docker compose file, however. I had to add the Authentik network to my app's container, and add this at the bottom:
Name of the network was ascertained by doing a
docker network ls
while Authentik was running. That told me the name of the Authentik network. I then modified myapplication.yaml
so it looked at the container name instead oflocalhost
. I was able to obtain the container name of Authentik's "server" container viadocker container ls
. Hope this helps someone e…