Skip to main content
Question

"A Problem occurred! Please try again later"

  • May 6, 2026
  • 2 replies
  • 38 views
A
Do Gooder (Customer)

Users are reporting an error trying login using SSO. Some users believe this has been happening for about a week, others first noticed today. Personally, I first encountered it today. 


"A Problem occurred! Please try again later"
“Unexpected error occurred when authenticating with identity provider”

The resolution has been simply to close the browser and try again.

Is this typical and expected behavior for IFS?

*Our IFS go-live was 4/1/2026. I was brand new to IFS at Go-Live I was not part of the initial project team. Just to give context. 

 

2 replies

Udara Hasantha
Do Gooder (Customer)
Forum|alt.badge.img+4

Hi ​@acztjohn 
 

Since this started happening a week ago (one month after go-live), it is very common for this to be related to Token Lifetimes. Often, initial tokens are set to expire in 30 days. You hit your 30-day mark on May 1st.

You may check with your IT Team if any Certificates or Client Secrets in the Azure App Registration (for IFS) were set to a short duration, or if a global policy changed on May 1st.

Plus, share ifs-auth or oidc pod logs with IFS and have a RCA.

regards

Udara. 

    ashen_malaka_ranasinghe
    Hero (Employee)
    Forum|alt.badge.img+12

    Hi ​@acztjohn,

    The error:

    “Unexpected error occurred when authenticating with identity provider”

    comes from the IFS IAM (Keycloak) → external IdP (e.g., Azure AD) login flow.

    This error occurs when:

    • IFS IAM fails to complete login with the identity provider
    • Or receives an unexpected/invalid token response from Azure AD

    It seems like authentication flow between IFS and IdP breaks temporarily. To get more information on this issue it is required to review ifsapp-iam pod logs when issue occurs.

    Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
    Terms & ConditionsAccessibility statement