Hello! Hope everyone is having a great Thursday.
I’m hoping someone here has run into the same (or a similar) issue our team is hitting with SAML SSO on Next-Gen apps using Microsoft Entra.
When SAML SSO first launched for Next-Gen, we had some early trouble, but we eventually worked through the gaps and contradictions in Knack’s documentation of the topic (with the help of Knack support) and got it working for two of our Next-Gen apps.
Recently, we got a request to set up SSO on a third Next-Gen app. We followed the exact same process that worked for the first two, but we’re now getting errors indicating that our SSO configuration is incorrect. After double-, triple-, and quadruple-checking, I can confirm the configuration is identical to our two working apps.
Knack support has noted that this is “out of their support scope,” which I don’t think is right since we successfully stood up two Knack apps with their help, so the process clearly works.
One thing worth mentioning: Knack’s documentation is tough to follow when you’re on Microsoft Entra, since the docs are written for Okta. Translating the terms and steps between the two platforms adds a lot of friction.
If anyone has experience with this or has found a workaround, I’d really appreciate any insight. This SSO issue is honestly the one thing keeping us from migrating some apps over to Next-Gen or exploring Next-Gen as an option.
Thank you,
Eli W