We would like to set up our self hosted Octopus instance to allow SSO via our ADFS system. We would like to configure it so that users browsing to the Octopus GUI are automatically redirected to our ADFS login page without any other interaction (ie any login dialogues, buttons, etc), are authenticated, then returned to the Octopus GUI having been logged in.
I have managed to get this working on a test instance of Octopus by using the built in Okta extension, and instead of configuring it to use Okta, pointing it at our ADFS OIDC configuration instead. This works well, and does exactly what we want.
However our problem is that on our live Octopus instance, we have the Active Directory extension enabled so that we can set permissions on AD groups. Currently users log in using the AD extension, but we would want to remove this ability in favour of SSO via ADFS instead. When this extension is enabled on the test instance, the SSO login flow changes to include an Octopus GUI page asking users to either ‘Sign in with a domain account’ or ‘Sign in with Okta’.
We’d really like to avoid this, as it’s confusing for our users. I assume this is happening because of the behaviour described here under Auto Login (‘this functionality is only active when there is a single, non forms-based authentication provider enabled’). However I also notice that under the settings for the Active Directory extension, there is an option where I can disable Forms Authentication for Domain Users. I might have thought that disabling this would return the behaviour to as we need it, but it doesn’t.
Is there any way to make this work? Or do we have to choose between using SSO, and being able to assign permissions via AD group in order to get a seamless login experience?
Alternately, is there any way to customise the login dialogue page which appears when both AD and Okta authentication is enabled?