-
Notifications
You must be signed in to change notification settings - Fork 475
Common Issues
It may be that the issues you're experiencing are not bugs but configuration issues. passport-saml uses a secure-by-default methodology. With every semver-major change, we attempt to change defaults and APIs to make them more secure. A semver-major upgrade is not automatic and stands a very good chance of not working without some code changes on your part. These changes will give you an opportunity to improve the security of your installation.
Please make sure to closely review the CHANGELOG file for release notes about major changes. This file is built automatically based on PRs, so every single change made to the project will be in there with links to the PR that caused the change for you to review.
Please see the following existing comments about things you might need to check to get your configuration working:
- https://github.com/node-saml/passport-saml/pull/840#issuecomment-1397272720
- https://github.com/node-saml/passport-saml/issues/863#issuecomment-1572095230
See comment from https://github.com/node-saml/passport-saml/discussions/671#discussioncomment-5261103 to see how to spot from authnresponse what sort of signatures it has and possibilities to configure @node-saml/passport-saml / @node-saml/node-saml if IdP configuration management is not an option for you or if you rather modify SP configuration.