Problem with team groups. List and AD

Hi,

I have two problems. My first: I changed my authentication mode to Domain. After i changed the mode i can no longer access the everyone team or octopus administrator team. I still can view and modify custom teams.

My second problem is with the domain authentication. I have a domain where the octopus server is located. This domain is oneway-trusted with my organisations domain. I am able to login with user accounts located in the octopus domain, but i can not login with accounts from my organisation domain. Is it possible to use oneway trust?

Hi,

My first problem is fixed. I checked the database and could see that there was a user in both groups that did not exist anymore (recomended action to remove admin user after change to AD-login). I turned off the octopus server and manually removed the user from the groups. Now I can access the groups in the portal.

My second problem still exist.

I also tried to change the login type. But apperantly, webauthenticationscheme command does not exist in my deployment?
Octopus.Server.exe configure --webAuthenticationScheme

Hi Viktor,

Thanks for reaching out. At the moment Octopus cannot work between trusted domains. It can only work with the domain where its sitting on. We have a github issue to review this behavior https://github.com/OctopusDeploy/Issues/issues/1737 . As you can see on the issue, it references many other github issues related to AD and trusted domains. We’ll work on a way to make it ease for users to create their own plugins for authentication. Though the issue is closed, its something we will be working on (probably on 3.1, but not 100% sure).

Sorry for the inconveniences

Dalmiro

Hi,

Well… That kind of sucks. Do you have any hits on when 3.1 will be released?

One does not simply tell developers to use an extra account for a specific service. But keep the good work up, I love OctopusDeploy. In the meanwhile, I will drink coffee and wait for 3.1.

Best regards

Hi Viktor,

I’m not 100% this will make it into 3.1, as we have other priorities for that version. We definitely want best for our users, and we know this scenario is something a lot of them want to see supported. So we will do something about it as mentioned by Paul on the github issue

Best timing I can give you for 3.1 is ‘Next couple of weeks’. Keep an eye on our blog for our pre-release blog post. The final release will be a week or so after that.

Best regards,

Dalmiro

PS: Thanks for saying you love Octopus even after I gave you bad news.