Skip to content

SSP 2.5 compatibility #1480

SSP 2.5 compatibility

SSP 2.5 compatibility #1480

Triggered via pull request March 14, 2026 19:31
Status Failure
Total duration 3m 49s
Artifacts 1

test.yaml

on: pull_request
Matrix: basic-tests
Security checks
35s
Security checks
Sanity checks
33s
Sanity checks
Matrix: conformance-suite
Quality control
50s
Quality control
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 6 warnings
MissingClassConstType: src/Services/AuthContextService.php#L22
src/Services/AuthContextService.php:22:24: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Services\AuthContextService::PERM_CLIENT" should have a declared type. (see https://psalm.dev/359)
PossiblyFalseArgument: src/Server/Validators/BearerTokenValidator.php#L115
src/Server/Validators/BearerTokenValidator.php:115:47: PossiblyFalseArgument: Argument 1 of array_change_key_case cannot be false, possibly array<array-key, mixed> value expected (see https://psalm.dev/104)
MissingClassConstType: src/Server/TokenIssuers/AbstractTokenIssuer.php#L11
src/Server/TokenIssuers/AbstractTokenIssuer.php:11:18: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Server\TokenIssuers\AbstractTokenIssuer::MAX_RANDOM_TOKEN_GENERATION_ATTEMPTS" should have a declared type. (see https://psalm.dev/359)
MissingClassConstType: src/Server/RequestRules/Rules/ClientIdRule.php#L33
src/Server/RequestRules/Rules/ClientIdRule.php:33:21: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Server\RequestRules\Rules\ClientIdRule::KEY_REQUEST_OBJECT_JTI" should have a declared type. (see https://psalm.dev/359)
MissingClassConstType: src/Server/RequestRules/Rules/ClientAuthenticationRule.php#L25
src/Server/RequestRules/Rules/ClientAuthenticationRule.php:25:21: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Server\RequestRules\Rules\ClientAuthenticationRule::KEY_CLIENT_ASSERTION_JTI" should have a declared type. (see https://psalm.dev/359)
MissingClassConstType: src/Repositories/ClientRepository.php#L38
src/Repositories/ClientRepository.php:38:24: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Repositories\ClientRepository::TABLE_NAME" should have a declared type. (see https://psalm.dev/359)
PossiblyFalseArgument: src/Helpers/Str.php#L27
src/Helpers/Str.php:27:13: PossiblyFalseArgument: Argument 1 of array_filter cannot be false, possibly array<array-key, mixed> value expected (see https://psalm.dev/104)
PossiblyFalseArgument: src/Forms/Controls/CsrfProtection.php#L42
src/Forms/Controls/CsrfProtection.php:42:48: PossiblyFalseArgument: Argument 1 of get_parent_class cannot be false, possibly class-string|object value expected (see https://psalm.dev/104)
MissingClassConstType: src/Factories/ClaimTranslatorExtractorFactory.php#L27
src/Factories/ClaimTranslatorExtractorFactory.php:27:21: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Factories\ClaimTranslatorExtractorFactory::CONFIG_KEY_MULTIPLE_CLAIM_VALUES_ALLOWED" should have a declared type. (see https://psalm.dev/359)
MissingClassConstType: src/Factories/ClaimTranslatorExtractorFactory.php#L25
src/Factories/ClaimTranslatorExtractorFactory.php:25:21: MissingClassConstType: Class constant "SimpleSAML\Module\oidc\Factories\ClaimTranslatorExtractorFactory::CONFIG_KEY_CLAIM_NAME_PREFIX" should have a declared type. (see https://psalm.dev/359)
Quality control
Process completed with exit code 1.
conformance-suite (v2.5.0)
Process completed with exit code 1.
conformance-suite (v2.4.5)
Process completed with exit code 1.
Sanity checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Security checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Syntax and unit tests, PHP 8.4,
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Syntax and unit tests, PHP 8.5,
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Syntax and unit tests, PHP 8.3,
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Quality control
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, codecov/codecov-action@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
build-data
32.2 MB
sha256:cb6092035d31e576ba9e8a4f753c6545613dac173a26a10ae5faf49ac67d06dc