Skip to content

Accept nullable service_name on SP configuration push#606

Open
kayjoosten wants to merge 2 commits into
mainfrom
feature/issue-589-service-name-config
Open

Accept nullable service_name on SP configuration push#606
kayjoosten wants to merge 2 commits into
mainfrom
feature/issue-589-service-name-config

Conversation

@kayjoosten

Copy link
Copy Markdown
Contributor

Gateway needs a display name to show during authentication (Gateway #624 already reads a service_name key from the pushed SP config JSON blob). Middleware was rejecting any config push containing that key, since ServiceProviderConfigurationValidator whitelists the exact set of allowed keys per service provider entry.

Add service_name as an optional, nullable string: omitted keys default to null before the key-set check runs, so existing config pushes that don't set it keep working unchanged.

Refs #589

Gateway needs a display name to show during authentication (Gateway
#624 already reads a `service_name` key from the pushed SP config
JSON blob). Middleware was rejecting any config push containing that
key, since ServiceProviderConfigurationValidator whitelists the exact
set of allowed keys per service provider entry.

Add `service_name` as an optional, nullable string: omitted keys
default to null before the key-set check runs, so existing config
pushes that don't set it keep working unchanged.

Refs #589
CI has been intermittently failing composer install: gitlab.irstea.fr
no longer resolves (DNS failure), and irstea/phpcpd-shim ships no
dist archive on Packagist, so composer always has to git-clone that
dead host for a fresh install. Runs only "pass" when the VCS cache
happens to be warm.

sebastian/phpcpd (the tool it shimmed) is back on Packagist directly,
but its last release pins sebastian/cli-parser ^1.0, which conflicts
with PHPUnit 10's ^2.0 requirement. phpcpd-next/phpcpd is an actively
maintained successor targeting PHP 8.5+, resolves cleanly, and ships
the same `phpcpd` binary our ci/qa/phpcpd script already calls.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant