[KeyVault] Get-default-policy returns gibberish in Python2
See original GitHub issueWhen I run get-default-policy
on Python 2 many of the fields are filled with gibberish such that I can’t immediately turn around and use it to get a self-signed cert:
{
"issuerParameters": {
"name": "U2VsZg=="
},
"keyProperties": {
"exportable": true,
"keySize": 2048,
"keyType": "UlNB",
"reuseKey": true
},
"lifetimeActions": [
{
"action": {
"actionType": "AutoRenew"
},
"trigger": {
"daysBeforeExpiry": 90
}
}
],
"secretProperties": {
"contentType": "YXBwbGljYXRpb24veC1wa2NzMTI="
},
"x509CertificateProperties": {
"keyUsage": [
"cRLSign",
"dataEncipherment",
"digitalSignature",
"keyEncipherment",
"keyAgreement",
"keyCertSign"
],
"subject": "Qz1VUywgU1Q9V0EsIEw9UmVkbW9uZCwgTz1Db250b3NvLCBPVT1Db250b3NvIEhSLCBDTj13d3cuY29udG9zby5jb20=",
"validityInMonths": 12
}
}
When I run on Python3:
{
"issuerParameters": {
"name": "Self"
},
"keyProperties": {
"exportable": true,
"keySize": 2048,
"keyType": "RSA",
"reuseKey": true
},
"lifetimeActions": [
{
"action": {
"actionType": "AutoRenew"
},
"trigger": {
"daysBeforeExpiry": 90
}
}
],
"secretProperties": {
"contentType": "application/x-pkcs12"
},
"x509CertificateProperties": {
"keyUsage": [
"cRLSign",
"dataEncipherment",
"digitalSignature",
"keyEncipherment",
"keyAgreement",
"keyCertSign"
],
"subject": "C=US, ST=WA, L=Redmond, O=Contoso, OU=Contoso HR, CN=www.contoso.com",
"validityInMonths": 12
}
}
(env) C:\Users\trpresco\Documents\github\azure-cli>az keyvault certificate get-default-policy
{
"issuerParameters": {
"name": "Self"
},
"keyProperties": {
"exportable": true,
"keySize": 2048,
"keyType": "RSA",
"reuseKey": true
},
"lifetimeActions": [
{
"action": {
"actionType": "AutoRenew"
},
"trigger": {
"daysBeforeExpiry": 90
}
}
],
"secretProperties": {
"contentType": "application/x-pkcs12"
},
"x509CertificateProperties": {
"keyUsage": [
"cRLSign",
"dataEncipherment",
"digitalSignature",
"keyEncipherment",
"keyAgreement",
"keyCertSign"
],
"subject": "C=US, ST=WA, L=Redmond, O=Contoso, OU=Contoso HR, CN=www.contoso.com",
"validityInMonths": 12
}
}
Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: dev_setup.py
CLI Version: What version of the CLI and modules are installed? (Use az --version
)
Answer here: azure-cli (2.0.4+dev)
acr (2.0.2+dev) acs (2.0.4+dev) appservice (0.1.4+dev) batch (2.0.2+dev) cloud (2.0.2+dev) component (2.0.2+dev) configure (2.0.4+dev) container (0.1.4+dev) core (2.0.4+dev) dla (0.0.4+dev) dls (0.0.4+dev) documentdb (0.1.4+dev) feedback (2.0.2+dev) find (0.2.1+dev) iot (0.1.4+dev) keyvault (2.0.2+dev) lab (0.0.3+dev) monitor (0.0.3+dev) network (2.0.4+dev) nspkg (3.0.0+dev) profile (2.0.4+dev) redis (0.2.1+dev) resource (2.0.4+dev) role (2.0.3+dev) shell (0.2.3+dev) sql (2.0.2+dev) storage (2.0.4+dev) taskhelp (0.1.2+dev) testsdk (0.1.0+dev) utility-automation (0.1.1) vm (2.0.4+dev)
OS Version: What OS and version are you using?
Answer here: Windows 10 CU
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: cmd.exe
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top GitHub Comments
Yup. Also added similar checks for --scaffold since it is a different code path.
Wanna add this too?