Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Tightned up the login-groups sub-section of the SSO section in forum.wiki. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
60c586d7d7954ec642dcffcaca0f4d38 |
User & Date: | wyoung 2018-08-09 06:17:34.831 |
Context
2018-08-09
| ||
06:59 | Minor improvements to forum.wiki ... (check-in: 635d2f63 user: wyoung tags: trunk) | |
06:17 | Tightned up the login-groups sub-section of the SSO section in forum.wiki. ... (check-in: 60c586d7 user: wyoung tags: trunk) | |
06:13 | Tightened up the MTA point in www/forum.wiki, and added a bit about digest delivery. ... (check-in: b51d6212 user: wyoung tags: trunk) | |
Changes
Changes to www/forum.wiki.
︙ | ︙ | |||
117 118 119 120 121 122 123 | to properly support SMTP email in this complex world we've built. As well, this design choice means you do not need to do duplicate configuration, such as to point Fossil at your server's TLS certificate private key in order to support users behind mail servers that require STARTTLS encryption. | | | 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 | to properly support SMTP email in this complex world we've built. As well, this design choice means you do not need to do duplicate configuration, such as to point Fossil at your server's TLS certificate private key in order to support users behind mail servers that require STARTTLS encryption. <h2>Setting up a Fossil Forum</h2> <h3>Permissions</h3> Fossil forums use the same role-based access control mechanism as for normal Fossil repository logins. There are several dedicated forum-related capability bits you can grant |
︙ | ︙ | |||
215 216 217 218 219 220 221 | this is that you have a public project where very few of those participating in the forum have special capability bits for project assets managed by Fossil, so you wish to segregate the two user sets. Yet, what of the users who will have logins on both repositories? Some users will be trusted with access to the project's main Fossil repository, and these users will probably also participate in the | | | < | | | | 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 | this is that you have a public project where very few of those participating in the forum have special capability bits for project assets managed by Fossil, so you wish to segregate the two user sets. Yet, what of the users who will have logins on both repositories? Some users will be trusted with access to the project's main Fossil repository, and these users will probably also participate in the project's Fossil-hosted forum. Fossil has a feature to solve this problem which is probably less well known than it should be, and which has been a feature of Fossil since April of 2011: Admin → Login-Group. This allows one Fossil repository to recognize users authorized on a different Fossil repository. <h3>Email Notification</h3> See [./emaildesign.md | the email notification design document] for now. More administration-oriented documentation TODO. |
︙ | ︙ |