Intermittent SAML failure in Integrated Developer Portal

I followed the YouTube video by @Dino-at-Google on how to use Okta as a SAML provider for the integrated developer portal.

The login seems to work 50% of the time. But intermittently, the user is presented with this:

InResponseToField of the Response doesn't correspond to sent message <code>


I've confirmed using Chrome developer tools that the code displayed on the screen is the code in the InResponseTo field of the SAML response returned by Okta.

Strangely, the login does appear to have worked, as when you navigate back to the home page and refresh, the user appears logged in.

0 3 238
3 REPLIES 3

John, let me see if I can get someone to take a deeper look at this for you.

John, it appears that the behavior you are observing and describing is related to a known problem in the handling of the SAML messages. I think the engineering team has produced the fix, and I am confirming that, and also confirming an expected release date.

ref: b/181112088

Thanks Dino.

I'll hold on until the fix is released. At least I know I am not doing something wrong.