DongHyeonkaandClaude Opus 5
e62bbb4df0
The authorized client repository is AuthenticatedPrincipalOAuth2AuthorizedClientRepository, keyed by principal with no session id in it, which is the mechanism behind the sharing problem Q1 and Q3 describe. Sharing a store does not fix a lookup key. Five problems on the way in: only build output was committed under bff/, a duplicate YAML key broke the image build and was invisible until the full log was captured, env placeholders without defaults broke the tests, actuator was behind the login redirect so a 200 was the login page, and the 117KB beans response failed through the proxy. Deploying two replicas made the login itself fail before any experiment started, because the authorization request lives in per-instance memory and the callback lands elsewhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
410 B
Docker
15 lines
410 B
Docker
FROM maven:3.9.11-eclipse-temurin-21-alpine AS build
|
|
WORKDIR /workspace
|
|
COPY pom.xml .
|
|
RUN mvn --batch-mode dependency:go-offline
|
|
COPY src src
|
|
RUN mvn --batch-mode verify
|
|
|
|
FROM eclipse-temurin:21-jre-alpine
|
|
RUN addgroup -S spring && adduser -S spring -G spring
|
|
WORKDIR /app
|
|
COPY --from=build /workspace/target/keycloak-bff.jar app.jar
|
|
USER spring:spring
|
|
EXPOSE 8083
|
|
ENTRYPOINT ["java", "-jar", "/app/app.jar"]
|