<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
"405 Method Not Allowed" Error when Accessing Miro
Single Sign-On
Okta Classic Engine
Okta Identity Engine
Overview

When trying to access the Miro application, users may receive a 405 Method Not Allowed error on the Miro side when either a new SAML integration of the Miro application in the Okta Integration Network (OIN) catalog or after the integration has been used for some time.


405 Error 

Applies To
  • Miro SAML Integration
  • Security Assertion Markup Language (SAML)
  • Okta Integration Network (OIN)
Cause

The OIN app for Miro comes with two fields for custom values: Custom ACS URL and Custom Entity ID. If these fields contain values that point to custom destinations that do not match the values in Miro or vice versa, the sign-in will fail with the 405 Method Not Allowed error.

Solution
  • When using the default values, ensure the Custom ACS URL and Custom Entity ID fields are empty on the Okta side so that they can revert to the default values of https://miro.com/sso/saml and https://miro.com/.
  • When using custom/non-default ACS URL and/or Entity ID values provided by Miro, configure the values accordingly under Applications > Applications > Miro (formerly RealtimeBoard) > Sign-On > Edit > Advanced Sign-on Settings. If needed, consult Miro to determine if the default or custom values are being used.

 

Advanced Sign-on Settings

 

Loading
"405 Method Not Allowed" Error when Accessing Miro