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

Handle path variable redaction collision #3567

Closed
adamcfraser opened this issue May 14, 2018 · 2 comments
Closed

Handle path variable redaction collision #3567

adamcfraser opened this issue May 14, 2018 · 2 comments

Comments

@adamcfraser
Copy link
Collaborator

When redacting multiple path variables with matching values and different redaction levels, it's possible to end up with incorrect redaction levels applied, because of the way mux provides the list of path variables as a map.

e.g. redacting :4985/foo/foo should redact the db as MD and the docid as UD, but ordering isn't guaranteed by the map iteration.

@adamcfraser adamcfraser added this to the 2.1.0 milestone May 14, 2018
@adamcfraser adamcfraser modified the milestones: 2.1.0, 3.0.0 May 14, 2018
@bbrks
Copy link
Member

bbrks commented May 14, 2018

This issue is not applicable until metadata redaction is supported and enabled.

@djpongh djpongh modified the milestones: 3.0.0, 2.2.0 May 30, 2018
@djpongh djpongh removed the P2: medium label Jun 7, 2018
@djpongh djpongh modified the milestones: 2.2.0, 2.x Jun 7, 2018
@djpongh djpongh modified the milestones: 2.x, Iridium Aug 9, 2018
@djpongh djpongh modified the milestones: Iridium, Cobalt Aug 20, 2018
@djpongh djpongh removed the P3: low label Aug 28, 2018
@djpongh djpongh modified the milestones: Cobalt, Mercury Dec 13, 2018
@adamcfraser
Copy link
Collaborator Author

Closing - can be revisited when MD redaction is added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants