I was attempting to use the CLI to create a DEK manually (Version 4.71)
`
confluent schema-registry dek create --kek-name --subject --version 1 --algorithm AES256_GCM
'
Whenever that gets called it's getting a 500 error and while debugging it I noticed this output (scrubbed)
POST /dek-registry/v1/keks/<kek-name>/deks HTTP/1.1
Host: <My Host>
User-Agent: Confluent-CLI/v4.71.0 (https://confluent.io; support@confluent.io)
Content-Length: 119
Accept: application/vnd.schemaregistry.v1+json,application/vnd.schemaregistry+json; qs=0.9,application/json; qs=0.5
Authorization: Bearer <token>
Content-Type: application/json
Target-Sr-Cluster: lsrc-gkmg1
Accept-Encoding: gzip
{"algorithm":"AES256_GCM","encryptedKeyMaterial":"","subject":"<subject>","version":1}
If I do the same post without the encryptedKeyMaterial property then it does look like it creates the key fine, so there is a work around calling the API direct.
I did come across #2811 that looked like it did some changes for algorithm but kept the encryptedKeyMaterial property as being sent in all cases.
I was attempting to use the CLI to create a DEK manually (Version 4.71)
`
confluent schema-registry dek create --kek-name --subject --version 1 --algorithm AES256_GCM
'
Whenever that gets called it's getting a 500 error and while debugging it I noticed this output (scrubbed)
If I do the same post without the encryptedKeyMaterial property then it does look like it creates the key fine, so there is a work around calling the API direct.
I did come across #2811 that looked like it did some changes for algorithm but kept the encryptedKeyMaterial property as being sent in all cases.