Fix sign‑in errors when using SSO to access the Flexera console

Title

You may see an error when you try to sign in to the Flexera console. This usually happens when your organization uses single sign‑on (SSO) and you’re signing in with a method that isn’t supported. This article explains the most common causes and how to fix them.

Solution

Don't use a username and password when SSO is enabled.
When SSO is set up for your organization, signing in with a username and password is turned off. All users, including admins, must use SSO.
Check if you belong to multiple organizations with different sign‑in requirements.
- If your default organization has SSO enabled, you must sign in using SSO. After signing in, you can switch to organizations that don’t use SSO.
- If your default organization doesn’t use SSO, sign in with your username and password. When you switch to an organization that uses SSO, the Flexera console redirects you to the SSO sign‑in page.
Don't use multi‑factor authentication (MFA) when SSO is enabled.
If your organization uses SSO, you can’t sign in with MFA.
Use the correct MFA token if SSO isn’t enabled.
MFA tokens are specific to both a user and an organization. Make sure you use the token associated with the organization you’re signing into.
If AWS is integrated, verify that your AWS Active Directory username matches your email address in Flexera.
Your Active Directory account must use the same email address that appears in the Flexera console. You can view user information by selecting the user icon > Settings > Organization > Users.
If Azure is integrated, confirm that the Identifier (Entity ID) URL is correct in Azure AD.
If the Identifier (Entity ID) is incorrect or blank, you may see an error similar to:

AADSTS650056: Misconfigured application. This could be due to one of the following: the client has not listed any permissions for 'AAD Graph' in the requested permissions in the client's application registration. Or, the admin has not consented in the tenant. Or, check the application identifier in the request to ensure it matches the configured client application identifier. Or, check the certificate in the request to ensure it's valid. Please contact your admin to fix the configuration or consent on behalf of the tenant. Client app ID: Idl xxxxx.

The correct Entity ID URL is:

https://console.spotinst.com/auth/saml

If it’s incorrect, delete the existing Flexera SAML app in Azure AD and recreate it using the correct URL.

Outcome

After you correct the sign‑in method, authentication settings, or Entity ID configuration, you should be able to sign in to the Flexera console without errors.

Was this helpful?

Support Hub

Product

Ocean

Visibility

Guest

URL Name

Fix-sign-in-errors-when-using-SSO-to-access-the-Flexera-console

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Revenera Assistant

Related Articles

Please wait...

Case id: 00001065