[SAML Platform Authentication] Upgraded Lifetime to latest version and now can't generate Token
Web icon
Forge component by Alexandre Costa
Application Type
Traditional Web

We have opened an urgent ticket, but wanted to see if the community has experienced this.  

After upgrading LifeTime 11.11.x with Platform 11.14.0, we are now getting redirected to the "CentralizedLogin_AuthCodeFlow_CodePart.aspx" page in Service Center instead of getting the SAML redirect and generating our token.  

Has anyone corrected this issue?  The token generation was working before we upgraded.

We were able to fix this issue.  We were able to finally get into Service Center of LifeTime and publish the new version of the platform app.  We still have the case open because we were not able to use the admin user in any fashion to get into service center.

Hi Jeremy,

We are also facing the same issue , After upgrading LifeTime 11.11.0 with Platform 11.15.0, and getting redirected to "CentralizedLogin_AuthCodeFlow_CodePart.aspx" page in Service Center instead of getting the SAML redirect and generating our token.

Any idea how to fix this?.

Thanks and Regards,

Samsuddin Chisti

You have to upgrade to the latest version of this component.  OS changed the way apps login with Service Center credentials and the latest version fixes that.  The issue we had was getting logged into lifetime to be able to publish the app since we couldn't login with our admin credentials. We were very lucky that one of our admins still had a valid token and was able to use it to get into lifetimes service center.  We put in a case and were told this is not a supported forge component for OutSystems support.  As far as I have found, there is no way to login with local admin credentials since the SAML auth provider bypasses the local login.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.