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

Service metadata endpoints must reject the presence of filter query param #60

Closed
jgomer2001 opened this Issue Nov 27, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@jgomer2001
Collaborator

jgomer2001 commented Nov 27, 2017

Related #33

The following statement applies for all metadata endpoints (/ServiceProviderConfig, /Schemas, and /ResourceTypes ) not only the last one.

If a "filter" is provided, the service provider SHOULD respond with HTTP status code 403 (Forbidden) to ensure that clients cannot incorrectly assume that any matching conditions specified in a filter are true. (section 4 of RFC 7644)

A more appropriate implementation strategy should be a resteasy filter, not a weld interceptor.

@jgomer2001 jgomer2001 added this to the CE 3.2 milestone Nov 27, 2017

@jgomer2001 jgomer2001 self-assigned this Nov 27, 2017

jgomer2001 added a commit to GluuFederation/oxTrust that referenced this issue Dec 8, 2017

@jgomer2001 jgomer2001 closed this Dec 8, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment