Record request approval mechanism #4

New Issue

lauri · 2021-06-09T10:26:47Z

lauri commented

2021-06-09 10:26:47 +00:00

For better overview in database how a certificate got signed add attribute that has couple possible values:

autosign due to being allowed by AUTOSIGN_SUBNETS
kerberos for Kerberos authenticated machines
web for manually approved ones by pressing the green button in web
cli for manual sign via pinecone command line interface
token due to being verified by issued token

Finally make sure pinecone list shows the used mechanism and metric exporter exports the value as label

For better overview in database how a certificate got signed add attribute that has couple possible values: * `autosign` due to being allowed by AUTOSIGN_SUBNETS * `kerberos` for Kerberos authenticated machines * `web` for manually approved ones by pressing the green button in web * `cli` for manual sign via `pinecone` command line interface * `token` due to being verified by issued token Finally make sure `pinecone list` shows the used mechanism and [metric exporter](https://git.k-space.ee/pinecrypt/exporter) exports the value as label

marva was assigned by lauri

2021-06-09 10:27:26 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: pinecrypt/pinecrypt-gateway-backend#4