We have a customer that has different SAML providers for different groups. Currently, every SAML provider login button shows up on all STS login pages. Each group has their own STS and we would like to only display Group A Login button on Group A's STS. Is there a way to configure which SAML providers are shown on a given STS?
Question
Question
SSO set which LDSSTS sites show which SAML provider buttons
Replies
Hi Bert. Is SAML the only login method or are you also allowing Laserfiche authentication or Windows authentication?
They hope to eventually get all groups on SAML, but at this time some use SAML and some use Windows Auth.
Not the answer I was hoping for, lol. I was going to say with the newer versions of LFDSTS you can configure auto-login for SAML IdPs per STS, so that would be one way, but if you need to allow for other login methods I don't think it would work.
Anyone from Laserfiche, is this on the feature list to add? If not, please add it, we have multiple customers that are looking for this functionality.
With the latest LFDSSTS, you can fully rewrite the login page for each LFDSSTS site. But that might need someone with coding skills.
If you are familiar with cshtml, javascript, you can try to create your own login page with the following steps.
1. Copy C:\Program Files\Laserfiche\Directory server\Web\WebSTS\Views\Home\Login.cshtml to another file, e.g. C:\Program Files\Laserfiche\Directory server\Web\WebSTS\Views\Home\MyLogin.cshtml
1. Update content in MyLogin.cshtml.
What you need to do might be changing line 194 to something like
@foreach (var option in Model.FederationLoginOptions.Where(op => op.ProviderName == "Okta"))
replace the ProvideName with what you want. if you are not sure about the name, just open the login page, inspect the saml button you want to keep, there will be a "data-idp-name" holding the name.
1. Change C:\Program Files\Laserfiche\Directory server\Web\WebSTS\web.config
<add key="CustomLoginPage" value="MyLogin" /> <!-- remark no .cshtml -->
When anything unexpected happened, try to revert this change, check if issue still exist.