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

APIv1 metadata controller breaks on individual entity metadata #2

Open
vladimir-mencl-eresearch opened this issue Jun 1, 2020 · 0 comments

Comments

@vladimir-mencl-eresearch
Copy link
Contributor

Imported from upstream #162

I ran into this when exploring the REST API: the APIv1 metadata controller returns as the last entry of the list:

{"name":"entity","description":"SAML 2 compliant metadata snippet for specific entity descriptor ID","format":"xml","type":"entity","functioning":true,"link":"https://registry.tamaki.dev.tuakiri.ac.nz/federationregistry/api/v1/metadata/entity"}

But, when accessing the /federationregistry/api/v1/metadata/entity link, I only get

HTTP Status 400 -
type Status report
message

description The request sent by the client was syntactically incorrect.
Apache Tomcat/7.0.39

When I add the ID of an EntityDescriptor as an parameter, I do correctly get the metadata for that entityDescriptor:

https://registry.tamaki.dev.tuakiri.ac.nz/federationregistry/api/v1/metadata/entity/8

But it looks like the API controller is missing functionality to return a JSON list of entities with links to individual entity metadata URLs, similar to what other controllers do... looks like broken API to me.

Note: this is not used by any client - would be there just for completeness of the API.

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

1 participant