Hi, Probably missing something really simple but can't see what. I'm following the saml flow diagram and have got to a point using BoxyHQ where it calls to get the oauth/token which returns a code successfully. When it then calls back into the thirdPartySignInUpPOST override, the input into the override has a code but the authCodeResponse is undefined, which then passes through to getProfileInfo where the accessTokenAPIResponse is also undefined and can't retrieve userInfo from BoxyHQ because the .accessToken isn't defined. I've tried the same calls to my local BoxyHQ running in docker and I get a response correctly with an access token returned. I have based a lot of this off the jackson-supertokens-express example. Is there any reason that it would be undefined?

hey @bradvrm

Ahh i see, when I console.log inside getProfileInfo the whole response is undefined

hmm. Interesting

It's essentially a copy from the API set up in the jackson-supertokens-express example. I've ported that out of that project and into my existing supertokens API code written in express, but then running the UI through the jacksons-supertoken-express example on it's own. Port numbers etc all match, it's just the final step of getting profile info to create the user in my postgres db for supertokens that seems to fall over.

have you created a tenant in boxy server?

yeah, I can also get an access token back via postman if i call my local boxy server too, using the same body as I have defined in AccessTokenAPI Params

ok great!

i knew it would be something simple 😂 thank you for looking through it anyway 🙂

yea.. it's usually silly mistakes like this. haha