Fossil SCM
Tightned up the login-groups sub-section of the SSO section in forum.wiki.
Commit
60c586d7d7954ec642dcffcaca0f4d384f7e37cdfeb6121adbedbca359f0d5c7
Parent
b51d62122312698…
1 file changed
+6
-7
+6
-7
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -119,11 +119,11 @@ | ||
| 119 | 119 | configuration, such as to point Fossil at your server's TLS |
| 120 | 120 | certificate private key in order to support users behind mail |
| 121 | 121 | servers that require STARTTLS encryption. |
| 122 | 122 | |
| 123 | 123 | |
| 124 | -<h2>Setting up aFossil Forum</h2> | |
| 124 | +<h2>Setting up a Fossil Forum</h2> | |
| 125 | 125 | |
| 126 | 126 | <h3>Permissions</h3> |
| 127 | 127 | |
| 128 | 128 | Fossil forums use the same role-based access control mechanism as |
| 129 | 129 | for normal Fossil repository logins. |
| @@ -217,16 +217,15 @@ | ||
| 217 | 217 | assets managed by Fossil, so you wish to segregate the two user sets. |
| 218 | 218 | |
| 219 | 219 | Yet, what of the users who will have logins on both repositories? Some |
| 220 | 220 | users will be trusted with access to the project's main Fossil |
| 221 | 221 | repository, and these users will probably also participate in the |
| 222 | -project's Fossil-hosted forum. | |
| 223 | - | |
| 224 | -Fossil has a feature to solve this problem that is probably less well | |
| 225 | -known than it should be, which has been in the software since April of | |
| 226 | -2011: Admin → Login-Group, which allows one Fossil repository to | |
| 227 | -recognize users authorized on another Fossil repository. | |
| 222 | +project's Fossil-hosted forum. Fossil has a feature to solve this | |
| 223 | +problem which is probably less well known than it should be, and which | |
| 224 | +has been a feature of Fossil since April of 2011: Admin → | |
| 225 | +Login-Group. This allows one Fossil repository to recognize users | |
| 226 | +authorized on a different Fossil repository. | |
| 228 | 227 | |
| 229 | 228 | |
| 230 | 229 | <h3>Email Notification</h3> |
| 231 | 230 | |
| 232 | 231 | See [./emaildesign.md | the email notification design document] for now. |
| 233 | 232 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -119,11 +119,11 @@ | |
| 119 | configuration, such as to point Fossil at your server's TLS |
| 120 | certificate private key in order to support users behind mail |
| 121 | servers that require STARTTLS encryption. |
| 122 | |
| 123 | |
| 124 | <h2>Setting up aFossil Forum</h2> |
| 125 | |
| 126 | <h3>Permissions</h3> |
| 127 | |
| 128 | Fossil forums use the same role-based access control mechanism as |
| 129 | for normal Fossil repository logins. |
| @@ -217,16 +217,15 @@ | |
| 217 | assets managed by Fossil, so you wish to segregate the two user sets. |
| 218 | |
| 219 | Yet, what of the users who will have logins on both repositories? Some |
| 220 | users will be trusted with access to the project's main Fossil |
| 221 | repository, and these users will probably also participate in the |
| 222 | project's Fossil-hosted forum. |
| 223 | |
| 224 | Fossil has a feature to solve this problem that is probably less well |
| 225 | known than it should be, which has been in the software since April of |
| 226 | 2011: Admin → Login-Group, which allows one Fossil repository to |
| 227 | recognize users authorized on another Fossil repository. |
| 228 | |
| 229 | |
| 230 | <h3>Email Notification</h3> |
| 231 | |
| 232 | See [./emaildesign.md | the email notification design document] for now. |
| 233 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -119,11 +119,11 @@ | |
| 119 | configuration, such as to point Fossil at your server's TLS |
| 120 | certificate private key in order to support users behind mail |
| 121 | servers that require STARTTLS encryption. |
| 122 | |
| 123 | |
| 124 | <h2>Setting up a Fossil Forum</h2> |
| 125 | |
| 126 | <h3>Permissions</h3> |
| 127 | |
| 128 | Fossil forums use the same role-based access control mechanism as |
| 129 | for normal Fossil repository logins. |
| @@ -217,16 +217,15 @@ | |
| 217 | assets managed by Fossil, so you wish to segregate the two user sets. |
| 218 | |
| 219 | Yet, what of the users who will have logins on both repositories? Some |
| 220 | users will be trusted with access to the project's main Fossil |
| 221 | repository, and these users will probably also participate in the |
| 222 | project's Fossil-hosted forum. Fossil has a feature to solve this |
| 223 | problem which is probably less well known than it should be, and which |
| 224 | has been a feature of Fossil since April of 2011: Admin → |
| 225 | Login-Group. This allows one Fossil repository to recognize users |
| 226 | authorized on a different Fossil repository. |
| 227 | |
| 228 | |
| 229 | <h3>Email Notification</h3> |
| 230 | |
| 231 | See [./emaildesign.md | the email notification design document] for now. |
| 232 |