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 passport-saml is configured with a privateCert, the generated metadata does not include the corresponding public certificate.
It would be useful to either have another parameter we could pass to include the public certificate in the metadata, or if it would be added automatically if the privateCert file contained both the private key and the public cert.
The text was updated successfully, but these errors were encountered:
For anyone else who comes across this issue - you can get the key to show up in the metadata by also configuring decryptionPvk and providing the certificate in the generateServiceProviderMetadata. It doesn't appear to be possible to only have the key present for signing, or to have different signing and decryption keys.
If passport-saml is configured with a privateCert, the generated metadata does not include the corresponding public certificate.
It would be useful to either have another parameter we could pass to include the public certificate in the metadata, or if it would be added automatically if the privateCert file contained both the private key and the public cert.
The text was updated successfully, but these errors were encountered: