Remove "Login" field after SAML integration.
Have the option to only allow authentication through SAML once it's integrated.
Welcome to our community!
Duplicates 2
Separate Pages for OAuth Sources
Allow re-arranging the login options on the ScreenConnect login screen when using alternate auth methods like SAML.
Would like to make the SAML login the first login on the screen on the screenconnect login. Optionally, would like to remove the standard login or otherwise hide it when we have SAML enabled and working.
Replies 25
Yeah this would definitely be a good feature. Even at least removing the Forgot Password? option as this wouldn't be service by Control at all.
For those who want to hide the Forgot Password? link, simply go to Admin > Appearance and edit the LoginPanel.ForgotPasswordLinkButtonText field and ensure that it is empty (no value).
Hope that helps.
I found that the best option is to set LoginPanel.ForgotPasswordLinkVisible to false because that will disable the link entirely rather than just removing the text.
SSO has to be initiated somewhere. Normally that would be done from an SSO portal/landing page with all your apps on it. Clicking on the Screenconnect link would take you directly to being logged in without using the login page at all. I've tested that, it does work. The larger issue with options on the login page is user confusion, or on the flip side if you have multiple external providers, leaking information about your clients and what login options are available. I've changed my login page to remove those, as opposed to removing the L/P.
If you're really desperate to remove the L/P prompt, you should be able to comment out the part of login.aspx that displays it. Should be lines 84-92 or thereabouts depending on your version.
Starting at: "$form({ _commandName: 'SubmitLogin' }, ["
Ending at: "])," that's indented to the same level.
There would still be a landing page where you would have to click the SSO button though, right? More ideal is an option to set SSO only so you're auto signed in without the SignIn landing page.
If you're really desperate to remove the L/P prompt, you should be able to comment out the part of login.aspx that displays it. Should be lines 84-92 or thereabouts depending on your version.
Starting at: "$form({ _commandName: 'SubmitLogin' }, ["
Ending at: "])," that's indented to the same level.
I would like to second this. When using certain browsers with SSO (Azure AD in our case) if you go back to the login screen it auto populates your SSO string in the user name field and this can cause consistent sign in issues with non-tech savvy people. For example if your company uses this tool for IT personal and also for secure remote connection for maintenance staff to access the computer running HVAC control software. The Maintenance staff won't realize how to get around this and sign in with a different user. This is consistently generating some tickets for our Helpdesk.
We are increasingly giving Client end-users access to their computers via Control, and would love to give access via OAuth to Office 365 for some of the clients. However, this is currently not a workable solution because each different OAuth source creates a new login button. If there were a way to have it only display each client button on different named pages, or named themes it would be great. We could give the client a link like https://control.url/ClientA and it would show them only their own login button.