Fossil

Check-in [dd0a2dd3]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Expanded the SSO discussion in the new forum.wiki document
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:dd0a2dd3d3bb84995cf62671fdc0b4189988b78d1a01f1a51bd7457634e7ffb1
User & Date: wyoung 2018-08-08 19:09:26
Context
2018-08-08
19:22
Added the "Skin Setup" section to the new forum.wiki document check-in: 3ec8f0a9 user: wyoung tags: trunk
19:09
Expanded the SSO discussion in the new forum.wiki document check-in: dd0a2dd3 user: wyoung tags: trunk
18:58
Fixed some incorrect uses of Markdown backticks in a document declared as wiki format. check-in: 76ca1f82 user: wyoung tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/forum.wiki.

119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135

136
137



138
139
140
141


142
143
144
145
146
147
148
to grant the Moderate Forum capability (5) to an uncommonly
highly-trusted user.


<h3>Single Sign-On</h3>

If you choose to host your discussion forums within the same repository
as your other Fossil-managed content, you inherently have a single
sign-on system. Contrast a mailing list or a third-party forum system,
where you either end up with two seaprate user tables and permission
sets, or you must go to significant effort to integrate the two login
systems.

You may instead choose to host your forums in a separate repository from
your other assets, as may be done for a public project where very few of
those participating in the forum have special permissions for assets
managed by Fossil for the project itself.


Or, you may split the difference, hosting the forum in a separate



repository from the other assets yet use Fossil's login groups feature
to get single sign-on for both repositories.  You might choose to do
this to remove the forum traffic from the size of the main respository's
clones, for example.




<h3>Email Notification</h3>

See [./emaildesign.md | the email notification design document] for now.
More administration-oriented documentation TODO.








|
|
|
|
|

|
|
|
|
>

<
>
>
>
|
<
<
<
>
>







119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137

138
139
140
141



142
143
144
145
146
147
148
149
150
to grant the Moderate Forum capability (5) to an uncommonly
highly-trusted user.


<h3>Single Sign-On</h3>

If you choose to host your discussion forums within the same repository
as your project's other Fossil-managed content, you inherently have a
single sign-on system. Contrast third-party mailing list and forum
software where you either end up with two separate user tables and
permission sets, or you must go to significant effort to integrate the
two login systems.

You may instead choose to host your forums in a separate Fossil
repository from your other assets. A good reason to do this is that you
have a public project where very few of those participating in the forum
have special permissions for assets managed by Fossil for the project
itself, so you wish to segregate the two user sets.


Fossil offers a way to split the difference: you can host your forum in
a repository separate from your other Fossil-managed content yet still
have single sign-on for that common set of users that will have logins
on both repositories. Simply enable Fossil's login groups feature in



Admin &rarr; Login-Group, which allows one Fossil repository to
recognize users authorized on another repository.


<h3>Email Notification</h3>

See [./emaildesign.md | the email notification design document] for now.
More administration-oriented documentation TODO.