#12232: Validate catalog service credentials before saving to prevent silent failures & misleading errors#12233
Open
mahmoudadel54 wants to merge 1 commit intogeosolutions-it:masterfrom
Open
Conversation
…ving to prevent silent failures & misleading errors Description: - for authenticated services, add async credential check via WMS GetCapabilities request - Show clear, localized error messages instead of silent failures in SecurityPopup - Prevent invalid credentials from being stored or saved to maps - Add unit tests and i18n translations (EN, IT, FR, ES, DE)
6 tasks
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
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.
Description
This PR introduces real-time credential validation for authenticated catalog services. Previously, invalid credentials were accepted silently, leading to broken maps that non-admin users could not fix -if prevoisly configured-. Now, credentials are validated via a GetCapabilities request before being stored or saved, ensuring only valid configurations persist.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#12232
What is the new behavior?
2026-04-08.12-45-47.mp4
2026-04-08.12-46-44.mp4
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information