Error 400 in Okta when login using SSO with Liferay PaaS Console
Written By
Jorge García Jiménez
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- We integrated the Liferay PaaS console with our IDP trough SSO, but sometimes when trying to perform a log in we have a 400 error in OKTA.
- The flow to reproduce this issue is:
- log in SSO -> Ok
- log out
- log in SSO -> ERROR 400
- The error we got from OKTA is 400 (GENERAL_NONSUCCESS).
Resolution
- When performing a log in using a Single Sign On system, there are some SAML Assertions used to interchange information between the systems.
- The assertion from the Identity Provider must have the following fields:
- idp.subjectNameId, sent in the assertion as <saml:NameID> has to be an email address.
- firstName
- lastName
- email
Did this article resolve your issue ?