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
🐛 Bug Report
I am using a NodeJS backend and using the ThirdPartyEmailPassword recipe. We use Cisco Duo which has an OIDC discovery endpoint. The OIDC endpoint is case-senstive and it appears that the SuperTokens SDK converts all the characters in the URL to lower case which causes the IDP to return a 404 to the Supertokens SDK.
Useful informations
It pretty easy to repeat as I can take the OIDC url and use curl and it works fine. When I turn on debug messages on the supertokens node module, it spits out the URL it tries to use to get to the OIDC endpoint. The URL that shows up in the log is all lower case and If I take that URL directly and run curl with it, I also get a 404. The solution would be to not convert everything to lower case (or at least have an option to disable that).
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
I am using a NodeJS backend and using the ThirdPartyEmailPassword recipe. We use Cisco Duo which has an OIDC discovery endpoint. The OIDC endpoint is case-senstive and it appears that the SuperTokens SDK converts all the characters in the URL to lower case which causes the IDP to return a 404 to the Supertokens SDK.
Useful informations
It pretty easy to repeat as I can take the OIDC url and use curl and it works fine. When I turn on debug messages on the supertokens node module, it spits out the URL it tries to use to get to the OIDC endpoint. The URL that shows up in the log is all lower case and If I take that URL directly and run curl with it, I also get a 404. The solution would be to not convert everything to lower case (or at least have an option to disable that).
The text was updated successfully, but these errors were encountered: