/v2.0/certificates/* content is available even when token_format=UUID

Bug #1172052 reported by Jonathan Brownell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Won't Fix
Low
Unassigned

Bug Description

When I set the "token_format = UUID" in the Keystone configuration file, I can still access certificates located on disk via the REST API, despite the fact that they are not used for token signing.

Tags: pki
Revision history for this message
Adam Young (ayoung) wrote :

Why is this a bug?

Revision history for this message
Dolph Mathews (dolph) wrote :

I would expect those calls to return 404 if the results are otherwise meaningless / unconfigured.

Changed in keystone:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to keystone (master)

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

Changed in keystone:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
status: Confirmed → In Progress
Revision history for this message
Dolph Mathews (dolph) wrote :

Unassigning due to inactivity.

Changed in keystone:
assignee: Jeffrey Zhang (jeffrey4l) → nobody
status: In Progress → Triaged
tags: added: pki
Revision history for this message
Morgan Fainberg (mdrnstm) wrote :

PKI Tokens are deprecated, this extension likewise has been deprecated. Marking wont fix.

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

Other bug subscribers

Remote bug watches

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