Fix: Multiple Usage of Authenticators/Conditions in Authentication Sub-Flows #980
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.
What this PR does / why we need it:
Which issue this PR fixes: fixes #978
Special notes for your reviewer:
See Linked Bug-Ticket for detailed description of the problem.
Subflow-Executions are created without special configuration and then modified according the definiton in the input file. This requires the config-tool to query keycloak for the created execution. If we have multiple executions with different configs within one subflow they could not be found distinguished.
This PR adds a filter to the repository method to return executions with corect "alias"/"configuration" which finally allows users to have sub flows with usage of same authenticators/conditions.
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR