Skip to content
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

update of pull/1984 against 2.3 (A new MetaDataStorageHandlerDirectory class to load metadata from subdirectories) #2018

Conversation

monkeyiq
Copy link
Contributor

A new MetaDataStorageHandlerDirectory class to load metadata from subdirectories

This is a retarget of the original PR #1984 from simplesamlphp-2.1 to simplesamlphp-2.3.

This is another attempt at loading metadata from a subdirectory containing either php or xml files (or both). This specifically allows SP files to be broken out into one file per SP if there are a number of SPs and you wish to maintain a list using one file per SP.

It seems from the below links that the feature is desirable for a few users and having an implementation based on simplesamlphp-2.1 may allow a merge and closing of a long standing issue and long standing PR.

To be generic this also adds a file property to the config of the MetaDataStorageHandlerFlatFile class so it can be used to load the file instead of directly including it in the new MetaDataStorageHandlerDirectory class. This has the added advantage of a single code path to load those php files so other checks etc in the future can be all in one place.

I have tested with various php and xml files in /opt/sspdev/metadata/saml20-sp-remote.d and other metadata directories and inspected the results in the admin/federation page.

This relates to #1292 and #1368.

@monkeyiq monkeyiq merged commit 06c558d into simplesamlphp:simplesamlphp-2.3 Mar 20, 2024
11 of 12 checks passed
monkeyiq added a commit that referenced this pull request Mar 20, 2024
#2018

A new MetaDataStorageHandlerDirectory class to load metadata from
subdirectories
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant