Stuck on MultiSaml Implementation

[Huzaifa-Asif]

I am implementing Multi Saml flow using this module but i am facing issues, i have worked with this library deprecated version and it worked fine but when i upgraded the code to this module i start facing errors. So if you have test implementation for multi saml kindly share the code it will be helpful.

Plus i want to attach redis for cache management so if you have example of that how to integrate that in the flow it will be very helpful.

[srd90]

...i have worked with this library deprecated version and it worked fine but when i upgraded the code to this module i start facing errors. ...

You might have better luck getting at least some help if you would describe what errors you are running into. Include also version numbers (of your old passport-saml version also).

Plus i want to attach redis for cache management so if you have example of that how to integrate that in the flow it will be very helpful.

Do mean this well documented stuff for inresponseto validation (code snippet links point to version 4.0.4):

1. Implement this interface to wrap access to Redis
   

   passport-saml/README.md

   Lines 362 to 385 in 0c2cced

   	## Cache Provider
   	When `InResponseTo` validation is turned on, Passport-SAML will store generated request ids used in SAML requests to the IdP. The implementation of how things are stored, checked to see if they exist, and eventually removed is from the Cache Provider used by Passport-SAML.
   	The default implementation is a simple in-memory cache provider. For multiple server/process scenarios, this will not be sufficient as the server/process that generated the request id and stored in memory could be different than the server/process handling the SAML response. The `InResponseTo` could fail in this case erroneously.
   	To support this scenario you can provide an implementation for a cache provider by providing an object with following functions:
   	```javascript
   	{
   	saveAsync: async function (key, value) {
   	// saves the key with the optional value, returns the saved value
   	},
   	getAsync: async function (key) {
   	// returns the value if found, null otherwise
   	},
   	removeAsync: async function (key) {
   	// removes the key from the cache, returns the
   	// key removed, null if no key is removed
   	},
   	};
   	```
   	Provide an instance of an object which has these functions passed to the `cacheProvider` config option when using Passport-SAML.

2. And see this multisaml related note
   

   passport-saml/README.md

   Lines 107 to 109 in 0c2cced

   	The options passed when the `MultiSamlStrategy` is initialized are also passed as default values to each provider. e.g. If you provide an `issuer` on `MultiSamlStrategy`, this will be also a default value for every provider. You can override these defaults by passing a new value through the `getSamlOptions` function.
   	Using multiple providers supports `validateInResponseTo`, but all the `InResponse` values are stored on the same Cache. This means, if you're using the default `InMemoryCache`, that all providers have access to it and a provider might get its response validated against another's request. [Issue Report](https://github.com/node-saml/passport-saml/issues/334). To amend this you should provide a different cache provider per SAML provider, through the `getSamlOptions` function.

or do you mean something else?