If you're having difficulties with configuring the Miro SSO option, or your identity provider or if one of your end-users is unable to log into Miro this article might be helpful to troubleshoot.
Miro SSO and SCIM schema can be found here.
Miro Error Messages
Since our system rarely receives an explicit explanation from the Identity Provider system about the cause of the issue Miro messages do not show the exact reason either. We do however strive to update the information transfer process and make our messages clearer.
|
Error message |
Possible reasons |
|
This email account is not associated with an SSO account |
|
|
Something went wrong |
|
|
Something went wrong: |
IdP user profile is configured incorrectly or is not allowed to log in by the IdP |
|
Something went wrong: |
|
|
To authorize with SSO, please use the URL link provided by |
1. Your IdP is configured for IdP-initiated login only and you should not be able 2. You enabled SSO in your Miro account but did not configure it. In this case |
Azure or ADFS Error messages
Below you will find some advice from the community about specific errors:
“An error occurred. Contact your administrator for more information.” - community user case example
"Role not assigned" error - community article
Other possible errors - support.microsoft.com article
⚠️ Please be aware of which email address is transferred from the Identity Provider to Miro.
For instance, if your work station is authenticated with one set of credentials managed by Azure/ADFS but you are trying to use a different set to log into Miro the login attempt will fail, as the Identity Provider will transfer your main set of credentials and there will be a mismatch. This can also happen in the situation where your SSO administrator tests the login procedure under different user credentials.
If instead of the Single Sign-On methods in Azure you see the message:
The single sign-on configuration is not available for this application in the Enterprise applications experience. Miro (formerly RealtimeBoard) is a multi-tenant application and the application is owned by another tenant.
To change properties such as the reply URL and identifiers, contact the owner of the application.
it most likely means that there is already a configured Miro app in your Azure AD where our identifier (https://miro.com/) is used and therefore taken. As we know Azure is more or less unique in that this identity provider requires the identifier (Entity ID) to be unique.
To possibly resolve the situation we advise you to check the Enterprise Applications of your Azure instance and use the one that you already have configured for your Miro account settings.
Azure testing tool
To get to the testing tool, choose the Single Sign-In tab in the settings of your application and scroll down to the bottom of the section.
Azure suggests using the test login process to check the connection and troubleshoot an error message. After the test, you will be given instructions on how to solve the situation.
Test page in the Azure portal/console
Google SAML errors
Please refer to this section of Google documentation that lists possible errors and instructions on how to resolve the situation.
Miscellaneous Errors on the IDP side
General errors
- Please check that the IDP does not use ServiceProviderConfigs request because Miro does not support it.
If you're encountering an error not listed in this article please send a report to Miro Support and we will do our best to help you.