chore: wire IAM_URL into lims service - #20
Merged
Conversation
LIMS's authentication now goes through omnibioai-iam-client instead of decoding tokens locally (see omnibioai-lims PR10), which needs IAM_URL to reach the auth service for JWKS/revocation checks -- same var name/value every other IAM_URL consumer in this file already uses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
IAM_URL: http://auth-service:8001to thelimsservice's environment — same var name/value every otherIAM_URLconsumer in this compose file already uses.omnibioai-iam-client(RS256/JWKS + revocation checking against the auth service) instead of decoding tokens locally, and needs this URL to reach it.Test plan
origin/main— isolated, single-file change, no interaction with other in-flight work