Skip to content
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

[Question] saml20 saml.create API parameters #11

Open
petermikitsh opened this issue Aug 8, 2016 · 1 comment
Open

[Question] saml20 saml.create API parameters #11

petermikitsh opened this issue Aug 8, 2016 · 1 comment
Labels

Comments

@petermikitsh
Copy link

Hey Auth0,

I was using the SAML 2.0 saml.create(options, callback) API and I had some questions about options parameters. For some context, I'm looking to create encrypted, signed SAML2 assertions, and I looked at the unit tests for examples, but I still have questions.

Are the following descriptions correct for each options parameter?

  • options.cert: identity provider's x.509 certificate
  • options.key: identity provider's private key
  • options.encryptionPublicKey: service provider's public key
  • options.encryptionCert: service provider's x.509 certificate

To my understanding of SAML (which may be incorrect), assertions are encrypted using the service provider's public key / certificate (which are are the two encryption variables), and then later the service provider will decrypt using their private key. I'm not sure of the purpose for the other two parameters, cert and key.

Clarification on these parameters is appreciated. Thank you in advance!

@meirshal
Copy link

I'm also trying to understand that issue.
I assume that options.cert and options.key are the certificate and private key of the IdP that are used for signing the request, and that options.encryptionPublicKey is used for encryption, but I don't understand what options.encryptionCert is used for.
Can someone please explain? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants