Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help setting up SAML Jackson for idP login #875

Open
valtonia opened this issue Jan 15, 2025 · 3 comments
Open

Help setting up SAML Jackson for idP login #875

valtonia opened this issue Jan 15, 2025 · 3 comments

Comments

@valtonia
Copy link

Hi,
I'm testing Supertokens + Boxy SAML Jackson + MockSAML and have followed the instructions both on here and on the Boxy website and I have it working correctly for login initiated from the Supertokens pre-built UI but I can't get it working for an idP initiated login. As in going to MockSAML first and configuring it to call into Supertokens.

Are there any examples/instructions for how do to do this? I've searched on both the Supertokens and Boxy websites/githubs but haven't found anything related to this specific use-case. Is it even possible to make it work this way?

Thanks,
Alan.

@porcellus
Copy link
Collaborator

Hi,
We haven't really worked too much with idP initiated logins, but I think it's possible to make it work. That being said, I haven't seen it done myself.
As for how you can configure MockSAML/Boxy this way, I'd try looking in their docs. I think the flow of the calls is actually MockSAML -> Boxy -> ST (not MockSAML into ST).

While we do not have much of a guidance or an example built, if you encounter any errors or issues please let us know. I'd be happy to help you resolve them and add it to our docs later.

@valtonia
Copy link
Author

Yeah, I have it set up that way but when I initiate the login from MockSAML -> Boxy the request going into ST results in the context object having these properties/values:

{
    "action": "TO_AUTH",
    "showSignIn": false
}

This is after Boxy calls into auth/callback/boxy-saml in ST.

If I had to guess I'd say that MockSAML/Boxy isn't sending the correct params to ST but I haven't had a chance to dig into that yet.

@porcellus
Copy link
Collaborator

I'll try and dig into this over the weekend, it could help if you sent me:

  • where you are getting redirected and what params are present
    • a simple way is to get the har files of the flow. (here's a good description of how you can get them (although don't update them to zendesk).
  • any console logs from the frontend with debug logs enabled
  • any console logs from the backend with debug logs enabled
  • See here on how you can enable debug logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants