> -----Original Message----- > From: [email protected] On Behalf Of Stuart Cracraft > Sent: 25 November 2013 23:29 > > Hi, > > I have direction to: > > 1) use Trac within an SSL-only Apache environment (i.e. > all connections to the box are SSL-only. No non-SSL.)
As Dimitri already mentioned, just setup a global redirect to https. I have the following in my top-level config:- RewriteRule ^/(.*) https://my.server.net/$1 [R=permanent,L] > 2) use Trac within an LDAP group environment (i.e. only this > group or that group can use Trac to access a given repository.) Hmm, do you mean Trac "environments" or subversion "repositories" here? Personally I setup top-level LDAP authentication to access the server then use trac permissions to provide finer-grained authorisation for each project (I still want some users to admin their own projects at various levels). For example each project has a relatively limited number of "pigs" or "chickens" ~ only the pigs should be able to browse the source... ~ mark c > Thoughts? I haven't come up with something straightforward for > either and/or both of the above using Google, Trac docs, etc. > > On the good side of it, I do have Trac up, running to Subversion, > with a Postgres back-end and have been checking in a ton of code, > browsing the repository, etc. > > With the above #1/#2, the installation can be secured and > made group-centric. > > Thanks for any tidbits of profound knowledge related to > exorcising my technical > daemons which you might throw my way. > > Stuart > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
