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

Trying to use the SP & issues with metadata #41

Open
pjsg opened this issue Apr 27, 2018 · 2 comments
Open

Trying to use the SP & issues with metadata #41

pjsg opened this issue Apr 27, 2018 · 2 comments

Comments

@pjsg
Copy link

pjsg commented Apr 27, 2018

I'm trying to use the Mujina-SP as part of a test harness for a SAML IdP that I'm working on. The issue that I have is that I can't figure out how to programatically set the IdP metadata into the SP. In particular, this appears to be required in order to have the signatures verify correctly.

Unfortunately I can't (easily) have a static metadata file that I inject into the Mujina-SP as it contains variable data that is determined when I run the tests.

Any ideas?

@oharsta
Copy link
Member

oharsta commented May 5, 2018

The current codebase does not support programmatically altering the IdP metadata used by the SP.

If you want to have a go at it then you could use the hook in the WebSecurityConfigurer. You can add more MetadataProvider instances. If you autowire this MetadataProvider into the SpController along with the CachingMetadataManager Bean, then you can add an endpoint to change the metadata and call the refresh on the MetadataManager.

@oharsta
Copy link
Member

oharsta commented Oct 19, 2018

@pjsg Did you manage to implement this or did you find a workaround? Programmatically changing the IdP metadata is not on the roadmap, but I would welcome a PR.

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

No branches or pull requests

2 participants