Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using CruiseControl.Net for continuous integration which is now accessing the dashboard through login plugin, which in turn is authenticating and authorizing after verifying it with a set of users saved as XML file in the CruiseControl.Net server.

Now, i need to bring in Windows Authentication to the system whereby which CruiseControl.Net server webdashboard when accessed from a client machine(local machine associated with a common server), would be authenticated and be authorized to access the CruiseControl.Net features based on the authority of the logged in users.

Kindly guide me to go ahead with this, appreciate all kinds of resources that would be helpful for achieving this.


share|improve this question
I am facing the same issue more than a year later. I think the support for Windows authentication is not implemented at all. IIS puts the identity in HttpContext.User and this is never used in the source of ccnet. I found instead only the use of Cookies["CCNetSessionToken"]... Not sure how to add the functionality. – jdehaan Dec 28 '11 at 8:16

I just realized that there is a big obstacle: the security is implemented in the ccnet server, not in the webdashboard. That makes it quite difficult to integrate with windows authentication mode. Removing it from the ccnet server is not a good idea as the ccnet-tray tool accesses directly the server using .NET remoting and needs authentication... For me it sounds like there is no way to solve this without a big architectural change.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.