You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
\ if the private_key is encrypted (Optional. Added in version 1.6.0)\",\n \
37
-
\ }\n ````\n\nMSAL Python requires a \"private_key\" in PEM format.\nIf your\
38
-
\ cert is in PKCS12 (.pfx) format,\nyou can convert it to X.509 (.pem) format,\n\
39
-
by `openssl pkcs12 -in file.pfx -out file.pem -nodes`.The thumbprint is available\
40
-
\ in your app's registration in Azure Portal.\nAlternatively, you can [calculate\
41
-
\ the thumbprint](https://github.com/Azure/azure-sdk-for-python/blob/07d10639d7e47f4852eaeb74aef5d569db499d6e/sdk/identity/azure-identity/azure/identity/_credentials/certificate.py#L94-L97).\n\
42
-
\n\n\n## Support Subject Name/Issuer Auth with a cert in .pem[Subject Name/Issuer\
\n {\n\"private_key\": \"...-----BEGIN PRIVATE KEY-----... in PEM format\"\
37
+
,\n\"thumbprint\": \"An SHA-1 thumbprint such as A1B2C3D4E5F6...\"\n\
38
+
\ \"Changed in version 1.35.0, if thumbprint is absent\"\n \
39
+
\ \"and a public_certificate is present, MSAL will\"\n\"automatically\
40
+
\ calculate an SHA-256 thumbprint instead.\",\n\"passphrase\": \"Needed\
41
+
\ if the private_key is encrypted (Added in version 1.6.0)\",\n\"public_certificate\"\
42
+
: \"...-----BEGIN CERTIFICATE-----...\", # Needed if you use Subject Name/Issuer\
43
+
\ auth. Added in version 0.5.0.\n }\n ````\n\nMSAL Python requires a \"\
44
+
private_key\" in PEM format.\nIf your cert is in PKCS12 (.pfx) format,\nyou\
45
+
\ can convert it to X.509 (.pem) format,\nby `openssl pkcs12 -in file.pfx -out\
46
+
\ file.pem -nodes`.The thumbprint is available in your app's registration in\
47
+
\ Azure Portal.\nAlternatively, you can [calculate the thumbprint](https://github.com/Azure/azure-sdk-for-python/blob/07d10639d7e47f4852eaeb74aef5d569db499d6e/sdk/identity/azure-identity/azure/identity/_credentials/certificate.py#L94-L97).`public_certificate`\
52
48
\ (optional) is public key certificate\nwhich will be sent through 'x5c' JWT\
53
-
\ header only for\nsubject name and issuer authentication to support cert auto\
the certificate containing\nthe public key corresponding to the key used to\
49
+
\ header.\nThis is useful when you use [Subject Name/Issuer Authentication](https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/60)\n\
50
+
which is an approach to allow easier certificate rotation.\nPer [specs](https://tools.ietf.org/html/rfc7515#section-4.1.6),\n\
51
+
\"the certificate containing\nthe public key corresponding to the key used to\
56
52
\ digitally sign the\nJWS MUST be the first certificate. This MAY be followed\
57
53
\ by\nadditional certificates, with each subsequent certificate being the\n\
58
54
one used to certify the previous one.\"\nHowever, your certificate's issuer\
\ if the private_key is encrypted (Optional. Added in version 1.6.0)\",\n \
37
-
\ }\n ````\n\nMSAL Python requires a \"private_key\" in PEM format.\nIf your\
38
-
\ cert is in PKCS12 (.pfx) format,\nyou can convert it to X.509 (.pem) format,\n\
39
-
by `openssl pkcs12 -in file.pfx -out file.pem -nodes`.The thumbprint is available\
40
-
\ in your app's registration in Azure Portal.\nAlternatively, you can [calculate\
41
-
\ the thumbprint](https://github.com/Azure/azure-sdk-for-python/blob/07d10639d7e47f4852eaeb74aef5d569db499d6e/sdk/identity/azure-identity/azure/identity/_credentials/certificate.py#L94-L97).\n\
42
-
\n\n\n## Support Subject Name/Issuer Auth with a cert in .pem[Subject Name/Issuer\
\n {\n\"private_key\": \"...-----BEGIN PRIVATE KEY-----... in PEM format\"\
37
+
,\n\"thumbprint\": \"An SHA-1 thumbprint such as A1B2C3D4E5F6...\"\n\
38
+
\ \"Changed in version 1.35.0, if thumbprint is absent\"\n \
39
+
\ \"and a public_certificate is present, MSAL will\"\n\"automatically\
40
+
\ calculate an SHA-256 thumbprint instead.\",\n\"passphrase\": \"Needed\
41
+
\ if the private_key is encrypted (Added in version 1.6.0)\",\n\"public_certificate\"\
42
+
: \"...-----BEGIN CERTIFICATE-----...\", # Needed if you use Subject Name/Issuer\
43
+
\ auth. Added in version 0.5.0.\n }\n ````\n\nMSAL Python requires a \"\
44
+
private_key\" in PEM format.\nIf your cert is in PKCS12 (.pfx) format,\nyou\
45
+
\ can convert it to X.509 (.pem) format,\nby `openssl pkcs12 -in file.pfx -out\
46
+
\ file.pem -nodes`.The thumbprint is available in your app's registration in\
47
+
\ Azure Portal.\nAlternatively, you can [calculate the thumbprint](https://github.com/Azure/azure-sdk-for-python/blob/07d10639d7e47f4852eaeb74aef5d569db499d6e/sdk/identity/azure-identity/azure/identity/_credentials/certificate.py#L94-L97).`public_certificate`\
52
48
\ (optional) is public key certificate\nwhich will be sent through 'x5c' JWT\
53
-
\ header only for\nsubject name and issuer authentication to support cert auto\
the certificate containing\nthe public key corresponding to the key used to\
49
+
\ header.\nThis is useful when you use [Subject Name/Issuer Authentication](https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/60)\n\
50
+
which is an approach to allow easier certificate rotation.\nPer [specs](https://tools.ietf.org/html/rfc7515#section-4.1.6),\n\
51
+
\"the certificate containing\nthe public key corresponding to the key used to\
56
52
\ digitally sign the\nJWS MUST be the first certificate. This MAY be followed\
57
53
\ by\nadditional certificates, with each subsequent certificate being the\n\
58
54
one used to certify the previous one.\"\nHowever, your certificate's issuer\
0 commit comments