Intermittent SAML failure in Integrated Developer Portal

We have configured a number of integrated developer portals to use SAML for the IDP. After some initial success logging in, we start to get intermittent SAML failures that appear as "Metadata for issuer https://sts.windows.net/{our azure ad tenant ID guid}/ wasn't found" on a page with the URL "https://{random account number}.accounts.apigee.io/saml_error".

We also believe this same issue is causing the "Login With SAML" button to also intermittently not appear on the portal Sign In pages.

We've done quite a bit of internal debugging to ensure the issue is not in our configuration or provider, but have found no issues.

I'm curious on if this is related to the same issue as this community question https://www.googlecloudcommunity.com/gc/Apigee/Intermittent-SAML-failure-in-Integrated-Developer-Por...

edit: want to add that our issue is more frequently occurring than the post above. We have about a 25% success rate.

Solved Solved
0 1 180
1 ACCEPTED SOLUTION

Wow, that sounds frustrating.  25% success is not enough! 

I suggest that you connect immediately with Apigee support staff. They'll have access to system logs and will be able to diagnose this problem with you.  

View solution in original post

1 REPLY 1

Wow, that sounds frustrating.  25% success is not enough! 

I suggest that you connect immediately with Apigee support staff. They'll have access to system logs and will be able to diagnose this problem with you.