-
-
Notifications
You must be signed in to change notification settings - Fork 235
Description
We are having issues with SAML auth via AWS that started this morning. We use IDP auth so we go thru the Application Dashboard instead of logging in from the application. This has been working just fine, but started to fail this morning.
We updated to the latest and realized that there had been some security issues fixed and wondering if that is related, but we're not seeing any changes to the SAML Metadata nor have we deployed any changes (until today to try to figure out whats happening.
We construct out iDP properties this way
idpProperties: {
metadata: Config.CT_SAML_XML,
},
const idp = samlify.IdentityProvider(idpProperties);
The SP is constructed the same way but with entityId and assertionConsumerService values. And then we call parseLoginResponse on the SP and then pull the data out to use to do the login.
We're seeing ERR_UNDEFINED_SIGNATURE_VERIFIER_OPTIONS
Which seems to come from libsaml.ts and isnt something we can control
if (!opts.keyFile && !opts.metadata) {
throw new Error('ERR_UNDEFINED_SIGNATURE_VERIFIER_OPTIONS');
}