Decide on validation sets behaviour

Bug #1463748 reported by Stanislaw Pitucha
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Anchor
Won't Fix
Medium
Stanislaw Pitucha

Bug Description

The original validation sets behaviour was to sign the certificate if any of the validation sets passed completely.

This was intended to be used in scenarios where different groups of servers make different kind of requests to the same Anchor instance. For example operator could configure Anchor to sign certificates for hosts *.nv.domain if the request comes from a nova range and for hosts *.gl.domain if the requests comes from a glance range.

This was changed in commit 52fefc1ca6ea50786b50d473d4069fc1414ef4c7 so that requests require passing all validation sets.

There are two ways forwards I see:
- restore the original behaviour if needed, or
- remove validation sets, because they're not required anymore (merging all validators into one set doesn't change the behaviour)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to anchor (master)

Fix proposed to branch: master
Review: https://review.openstack.org/190086

Changed in anchor:
status: New → In Progress
Revision history for this message
Stanislaw Pitucha (stanislaw-pitucha) wrote :

The above fix is for the first scenario. It's not the only possible solution though.
Comments welcome!

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on anchor (master)

Change abandoned by Stanislaw Pitucha (<email address hidden>) on branch: master
Review: https://review.openstack.org/190086
Reason: Will be superseeded by the /v1 API patch.

Changed in anchor:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.