Yeah, it sorts them alphabetically :-( For some reason I can't update scenario one at the moment (might be firewall issues), so if I update the other two scenarios to use numbers, then scenario one will be out of order.
Craig ________________________________ From: kowrip <[email protected]> To: ccnet-user <[email protected]> Sent: Fri, 11 December, 2009 11:10:07 AM Subject: [ccnet-user] Re: Security Setup For 1.5 CTP One other note. Scenarios #2 and #3 are out of order on the web page. On Dec 10, 4:19 pm, Craig Sutherland <[email protected]> wrote: > Hi, > > You are right, the documentation is very out of date (the security scenario > was from a pre-CTP build). > > I have updated scenario one so it validates, plus finally copied over the > other two scenarios (these were on my blog) and updated them so they all > validate. I haven't had time to test them, but as they are valid they should > work. > > I am also in the process of updating the configuration elements - I'll expand > the examples to show how they work in context. > > Hope this helps, > > Craig > > ________________________________ > From: kowrip <[email protected]> > To: ccnet-user <[email protected]> > Sent: Fri, 11 December, 2009 5:53:14 AM > Subject: [ccnet-user] Security Setup For 1.5 CTP > > Hi All. I'm new to the group, but usage of CC.NET has been growing at > my company pretty rapidly. I'm interested in testing the security > features of the 1.5 CTP release. However, the documentation is not > very helpful. I'm completely lost as to the actual element names and > where they go. The documentation gives no high-level example of > this. Also, the "Scenario One" example doesn't work either. The > author says to add a "sessionSecurity" element anywhere as a child > node of the "cruisecontrol" element. However, CCValidator complains > about this being an invalid element. Can anybody provide some > guidance for using this feature ? Any help is greatly appreciated. > Thanks.
