Repository navigation
Alternative token exchange #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
floeschau
wants to merge
14
commits into
main
Choose a base branch
from
feature/token-exchange-cd-ttd
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
372e649
Skip token exchange for OGC API if token was issued by iam.terradue.com
floeschau ba9966c
Changes for test deployment (Terradue)
floeschau ec90107
Changes for test deployment (Terradue) (2)
floeschau 88ead06
Changes for test deployment (Terradue) (3)
floeschau a26e596
Enabled Cross Domain Federation/Trusted Token Delegation
floeschau efa0559
Merge branch 'main' into feature/token-exchange-cd-ttd
floeschau 366a1bd
Merge branch 'main' into feature/token-exchange-cd-ttd
JanssenBrm 42fcf47
feat: add config property for token exchange method
floeschau 1945c52
Merge origin/main into feature/token-exchange-cd-ttd
JanssenBrm f2a6442
chore: cleanup dummy env
JanssenBrm 14c757a
fix: consistent mapping with db model
JanssenBrm 970dcab
chore: fixed linting issues
JanssenBrm 3200340
chore: fixed linting issues
JanssenBrm 833d095
Merge branch 'main' into feature/token-exchange-cd-ttd
JanssenBrm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| version: "3.9" | ||
|
|
||
| volumes: | ||
| apex-db-data: | ||
|
|
||
| services: | ||
| db: | ||
| image: postgres:15 | ||
| restart: unless-stopped | ||
| environment: | ||
| POSTGRES_USER: apex_user | ||
| POSTGRES_PASSWORD: apex_pass | ||
| POSTGRES_DB: apex_db | ||
| ports: | ||
| - "5432:5432" | ||
| volumes: | ||
| - apex-db-data:/var/lib/postgresql/data | ||
| healthcheck: | ||
| test: ["CMD-SHELL", "pg_isready -U apex_user -d apex_db"] | ||
| interval: 5s | ||
| timeout: 5s | ||
| retries: 10 | ||
|
|
||
| app: | ||
| build: | ||
| context: . | ||
| dockerfile: dockerfile | ||
| image: apex-dispatch-api:latest | ||
| restart: unless-stopped | ||
| environment: | ||
| APP_ENV: development | ||
| KEYCLOAK_HOST: ${KEYCLOAK_HOST} | ||
| KEYCLOAK_REALM: ${KEYCLOAK_REALM} | ||
| KEYCLOAK_CLIENT_ID: ${KEYCLOAK_CLIENT_ID} | ||
| KEYCLOAK_CLIENT_SECRET: ${KEYCLOAK_CLIENT_SECRET} | ||
| DATABASE_URL: ${DATABASE_URL} | ||
| BACKENDS: '{"https://processing.geohazards-tep.eu": {"auth_method": "USER_CREDENTIALS", "token_provider": "gep", "token_prefix": ""}}' | ||
| depends_on: | ||
| db: | ||
| condition: service_healthy | ||
| ports: | ||
| - "${APP_PORT:-8000}:${APP_PORT:-8000}" | ||
| healthcheck: | ||
| # adjust path if your health endpoint differs | ||
| test: ["CMD-SHELL", "curl -f http://localhost:${APP_PORT:-8000}/health || exit 1"] | ||
| interval: 5s | ||
| timeout: 3s | ||
| retries: 12 | ||
|
|
||
| migrate: | ||
| image: apex-dispatch-api:latest | ||
| environment: | ||
| DATABASE_URL: ${DATABASE_URL} | ||
| depends_on: | ||
| db: | ||
| condition: service_healthy | ||
| # run the migration only after the app is reachable, then exit | ||
| entrypoint: ["/bin/sh", "-c"] | ||
| command: > | ||
| "alembic upgrade head" |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@floeschau - This. seems to be very specific for the terradue case and not OGC generic. Just for my understanding: in which case is the expecting issuer
iam.terradue.com? Probably missing something, but I would assume that theuser_tokenis always coming from APEx?