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
The above is awkward in the context of SAML 2.0 since the common use case for encryption is to encrypt something using the other party's public certificate, not their private key as well.
Also, some constructs are possible at compile-time, but then throw an exception at runtime:
The nice thing about these as well is that they remove the application's need to work with the Saml2X509CredentialType class, further simplifying their application.
The text was updated successfully, but these errors were encountered:
Saml2X509Credential
constructors are somewhat complicated to use.For example, there are possible constructs that don't make sense:
The above is awkward in the context of SAML 2.0 since the common use case for encryption is to encrypt something using the other party's public certificate, not their private key as well.
Also, some constructs are possible at compile-time, but then throw an exception at runtime:
When run, the above will error because no private key was supplied.
Both of these scenarios can be addressed by adding some simple static factories to
Saml2X509Credential
like:The nice thing about these as well is that they remove the application's need to work with the
Saml2X509CredentialType
class, further simplifying their application.The text was updated successfully, but these errors were encountered: