Our trac setup uses a .htpasswd files for authentication of users.

As you can see trac starts with a certain .htpasswd file for each project (Neotek, Onboard, playground)

/bin/tracd --protocol https --certfile /etc/letsencrypt/live/kokyou.dev/cert.pem --keyfile /etc/letsencrypt/live/kokyou.dev/privkey.pem \ 
--basic-auth=*,/srv/trac/.htpasswd,Neotek --basic-auth=*,/srv/trac/.htpasswd,Onboarding --basic-auth=*,/srv/trac/.htpasswd,playground -e /srv/trac/ \
--group tracd --user tracd --port=8080

The user can not easily set or change his password. Applying passwords is always done by the sites admin. If you want to choose your own password, you can
generate it via

{{{#!sh
htpasswd -c .htpasswd jane
htpasswd .htpasswd tarzan
}}}

The above two commands create a new .htpasswd file for jane and add another user named tarzan afterwards. The passwords are MD5 hashed.
You can send the .htpasswd file on a secure way to your site admin with an request for access rights to a given trac project.


[wiki:Workflows back]