
Currently, Single Sign-On is not supported. While Okta helps us overcome this with their SWA technology, it’s far from perfect, and does not allow us to put controls in place should someone try to access our account from your website directly. Would love to see support for SAML, especially if this issue was paired with #7


@Frantisek Please note that I saw your comment on a similar post requesting SAML/SSO asking if Sub-users (#7) would solve. It should be clear that sub-users alone are not going to fix the SSO issue, however I think it’s a great start. It’s common for applications that support SSO to have the admin sign up, often with username/password, then setup their ‘domain’ for SSO. This is where sub-users can come into play, and in theory provision users and permissions from the IdP.
I would like to see support for ADFS and Azure AD
SAML SSO and SCIM provisioning via Entra ID should be a startand feature in any application IT might use
Is there any traction on this? All net new SaaS products we onboard are required by internal policies to have SSO. If we were looking for a new monitoring vendor today UR would not qualify.

For me, its a real “red flag” that UTR doen’t have this, espically as there are some may modules out there for various programming languages that will do the “heavy lift” , I personally would like to see openid and googleID