| 1 | | soon |
| | 1 | Our trac setup uses a .htpasswd files for authentication of users. |
| | 2 | |
| | 3 | As you can see trac starts with a certain .htpasswd file for each project (Neotek, Onboard, playground) |
| | 4 | |
| | 5 | /bin/tracd --protocol https --certfile /etc/letsencrypt/live/kokyou.dev/cert.pem --keyfile /etc/letsencrypt/live/kokyou.dev/privkey.pem \ |
| | 6 | --basic-auth=*,/srv/trac/.htpasswd,Neotek --basic-auth=*,/srv/trac/.htpasswd,Onboarding --basic-auth=*,/srv/trac/.htpasswd,playground -e /srv/trac/ \ |
| | 7 | --group tracd --user tracd --port=8080 |
| | 8 | |
| | 9 | 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 |
| | 10 | generate it via |
| | 11 | |
| | 12 | {{{#!sh |
| | 13 | htpasswd -c .htpasswd jane |
| | 14 | htpasswd .htpasswd tarzan |
| | 15 | }}} |
| | 16 | |
| | 17 | The above two commands create a new .htpasswd file for jane and add another user named tarzan afterwards. The passwords are MD5 hashed. |
| | 18 | 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. |
| | 19 | |
