[seonghobae]

🚨 Severity: High
💡 Vulnerability: 런타임 시크릿(artifact token secret 및 tenant claims HMAC secret)을 환경 변수(application-buyer-demo.yml 내 @Value 기본값 설정)로 주입하는 방식은 컨테이너나 프로세스 환경에 민감한 정보가 유출될 위험이 존재했습니다.
🎯 Impact: 공격자가 프로세스 환경 변수를 탈취할 경우 토큰 생성이나 서명 로직을 우회할 수 있어 전체 권한 우회 및 문서 유출의 심각한 결과를 초래할 수 있습니다.
🔧 Fix:

• application-buyer-demo.yml에서 해당 시크릿 설정을 제거하여 Spring Boot configtree에서만 값을 가져오도록 변경했습니다.
• @Value 애너테이션에서 : 폴백(fallback)을 제거하여 누락된 경우 시작 시점에 즉시 실패하도록 강제(Fail-fast)했습니다.
• 관련 테스트(ProductionAuthReadinessConfigTest.java)를 수정하여 값이 누락되었을 때 컨텍스트 로드가 실패함을 올바르게 검증하도록 하였습니다.
• CHANGELOG.md 및 .jules/sentinel.md에 한국어로 변경 사항과 배운 점을 기록했습니다.
  ✅ Verification: mvn clean verify를 성공적으로 통과했으며 추가적인 유닛 테스트도 오류 없이 수행되었습니다.

---

PR created automatically by Jules for task 7758274103332140806 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2ea5a5ed-e43e-4b31-a917-27a6595eed20

📥 Commits

Reviewing files that changed from the base of the PR and between 06633a2 and 528b0b2.

📒 Files selected for processing (7)

• .jules/sentinel.md
• CHANGELOG.md
• src/main/java/com/clearfolio/viewer/artifact/ArtifactLinkService.java
• src/main/java/com/clearfolio/viewer/auth/TenantAccessService.java
• src/main/java/com/clearfolio/viewer/config/ProductionAuthReadinessConfig.java
• src/main/resources/application-buyer-demo.yml
• src/test/java/com/clearfolio/viewer/config/ProductionAuthReadinessConfigTest.java

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Closing as superseded by #482. The unique useful intent here—preventing the buyer-demo profile from restoring runtime signing-secret environment mappings—is now covered by #482's focused executable policy test. The additional @Value placeholder changes in this branch broaden the behavior into mandatory property resolution for every composition, mixing a minimal configuration repair with the separate production credential-registry migration. #482 remains the canonical bounded landing path; #319/#344/#354/#433 retain runtime credential authority.

[google-labs-jules]

Closing as superseded by #482. The unique useful intent here—preventing the buyer-demo profile from restoring runtime signing-secret environment mappings—is now covered by #482's focused executable policy test. The additional @Value placeholder changes in this branch broaden the behavior into mandatory property resolution for every composition, mixing a minimal configuration repair with the separate production credential-registry migration. #482 remains the canonical bounded landing path; #319/#344/#354/#433 retain runtime credential authority.

Understood. Acknowledging that this work is now superseded by #482 and stopping work on this task.