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
{{ message }}
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Depending on your setup, there's a decent chance that the key will have invalid characters and fail to serialize since we're using a raw URL. It just happens that for default Mongo setups you're ok since it will stringify the entire object.
Might I suggest using the clientId instead since that is more serializable? That's basically what we're doing in application code as a workaround (passing the option sessionKey: 'OIDC: {clientId}'). Alternatively, could do some escaping of the redirect url.
The text was updated successfully, but these errors were encountered:
Version: v3.0.4
Setup (not specific to these deps though):
express-session
v1.10.4connect-mongo
v0.8.2Repro:
connect-mongo
optionstringify: false
(details)Result:
The dotted field 'OIDC: {redirectUrl}' in 'session.OIDC: {redirectUrl}' is not valid for storage
I believe the default value for the session key here is at fault
(https://github.com/AzureAD/passport-azure-ad/blob/master/lib/oidcstrategy.js#L382):
Depending on your setup, there's a decent chance that the key will have invalid characters and fail to serialize since we're using a raw URL. It just happens that for default Mongo setups you're ok since it will stringify the entire object.
Might I suggest using the
clientId
instead since that is more serializable? That's basically what we're doing in application code as a workaround (passing the optionsessionKey: 'OIDC: {clientId}'
). Alternatively, could do some escaping of the redirect url.The text was updated successfully, but these errors were encountered: