-
Notifications
You must be signed in to change notification settings - Fork 2
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
Deploy Gaia-X Authority did document #175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please review comments provided
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The DID and private key are related not just to "registration service", but really to "dataspace authority" which is more than that. Names should reflect this
indeed, I renamed the |
@@ -0,0 +1,18 @@ | |||
name: "Generate key" | |||
description: "Generate key" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we extend this description
|
||
inputs: | ||
keyname: | ||
description: 'Name of the key file name' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: 'Name of the key file name' | |
description: 'Prefix for key file names' |
runs: | ||
using: "composite" | ||
steps: | ||
- name: 'Generate GAIA-X Authority key' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs generalisation
description: "Generate key" | ||
|
||
inputs: | ||
keyname: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keyname: | |
keyFileNamePrefix: |
.github/workflows/deploy.yaml
Outdated
- name: 'Generate Dataspace Authority key' | ||
uses: ./.github/actions/generate-key | ||
with: | ||
keyname: registrationservicekey |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keyname: registrationservicekey | |
keyname: authoritykey |
.github/workflows/deploy.yaml
Outdated
openssl ecparam -name prime256v1 -genkey -noout -out key.pem | ||
openssl ec -in key.pem -pubout -out key.public.pem | ||
docker run -i danedmunds/pem-to-jwk:1.2.1 --public --pretty < key.public.pem > key.public.jwk | ||
- name: 'Generate Participant's key' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- name: 'Generate Participant's key' | |
- name: 'Generate Participant key' |
} | ||
], | ||
"verificationMethod" = [ | ||
{ | ||
"id" = "#identity-key-1" | ||
"id" = "#identity-key-registration-service" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"id" = "#identity-key-registration-service" | |
"id" = "#identity-key-authority" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
open questions/comments addressed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with suggestions which can be discussed later, no action needed for this PR at the moment. Thank you.
variable "key_file_authority" { | ||
description = "name of a file containing the Registration Service private key in PEM format" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: By reading description and the variable name it gives the impression that authority and registration service are related as its usage registration service private key as per the description.
No action needed on this PR but we can discuss it later.
key_vault_id = azurerm_key_vault.registry.id | ||
count = var.key_file_authority == null ? 0 : 1 | ||
value = file(var.key_file_authority) | ||
key_vault_id = azurerm_key_vault.registrationservice.id |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Same as below comment, If registration service does not need a key vault, then maybe we do not deploy one for that and rename to authority
as currently in this PR registration service key vault is used to store authority did private key only.
No action for now can be discussed in a follow-up PR.
Deployment of GAIA-X Authority DID in Deploy pipeline.
DID document contains public key in the same format as Registration Service did document.
Further notes
registry
to eitherauthority
for did document resources andregistrationservice
for Registration Service resources for consistencybranches: [ main ]
from CD workflow to enable checks in all PRslinked to #151