Burp Suite User Forum

Create new post

Authentication bypass via OAuth implicit flow - SessionNotFound: invalid_request

XnterQ | Last updated: Apr 02, 2021 11:14AM UTC

Hi, The lab "Authentication bypass via OAuth implicit flow" is not working. After clicking "My account" page loads for few seconds and shows with error: SessionNotFound: invalid_request at Provider.getInteraction (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/oidc-provider/lib/provider.js:50:11) at Provider.interactionDetails (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/oidc-provider/lib/provider.js:228:27) at /home/carlos/oauth/index.js:160:34 at Layer.handle [as handle_request] (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/route.js:137:13) at setNoCache (/home/carlos/oauth/index.js:121:5) at Layer.handle [as handle_request] (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/route.js:137:13) at Route.dispatch (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/layer.js:95:5)

Michelle, PortSwigger Agent | Last updated: Apr 05, 2021 12:32PM UTC

Thanks for your message.

At which stage during the lab do you see this error? Can you describe the steps you have taken when the error occurs, please?

sabari | Last updated: Apr 21, 2021 06:49AM UTC

i have this error pls fix this

Michelle, PortSwigger Agent | Last updated: Apr 21, 2021 10:17AM UTC

Thanks for your message. We have not been able to recreate the error you are seeing, can you talk us through the steps you are taking when this happens or maybe send a screen recording to support@portswigger.net?

chronosz1 | Last updated: Aug 27, 2021 01:18PM UTC

HI portswigger community, i am facing this error in all labs, help me? SessionNotFound: invalid_request at Provider.getInteraction (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/oidc-provider/lib/provider.js:50:11) at Provider.interactionDetails (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/oidc-provider/lib/provider.js:228:27) at /home/carlos/oauth/index.js:160:34 at Layer.handle [as handle_request] (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/route.js:137:13) at setNoCache (/home/carlos/oauth/index.js:121:5) at Layer.handle [as handle_request] (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/route.js:137:13) at Route.dispatch (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/usr/local/nvm/versions/node/v12.19.0/lib/node_modules/express/lib/router/layer.js:95:5)

Michelle, PortSwigger Agent | Last updated: Aug 27, 2021 01:44PM UTC

Thanks for your message. We've just tested this with some different browsers and we haven't been able to replicate the issue. Which browser are you using? Do you see the same issue if you use a different browser (e.g. Burp's embedded browser)?

osman.h | Last updated: Oct 19, 2021 12:25AM UTC

i am using firfox browser ........ and i am phasing same issue please solve it

Michelle, PortSwigger Agent | Last updated: Oct 19, 2021 02:15PM UTC

Thanks for your message. In our tests here we have been able to use Firefox with this lab so this issue seems to be something specific to certain Firefox versions or configurations. If you use a different browser (e.g. Chrome or burp's embedded browser) you should be able to complete the lab. I hope this helps. please let us know if you have any questions.

tuandv | Last updated: Aug 24, 2022 03:45AM UTC

I just got this error, maybe because the timeout problem is too long, you can go back to the lab and start over.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.