Fossil

Check-in [bc303c0e]
Login

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

Overview
Comment:More SSO discussion improvements in forum.wiki
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:bc303c0ec006ab3109261788dcf99d71dc8b671df8dbfea68ac74b2922d0182f
User & Date: wyoung 2018-08-08 19:43:11
Context
2018-08-08
20:01
Enhance the /register page so that it also does email subscriptions if that is enabled for self-registered users. check-in: 2e308280 user: drh tags: trunk
19:43
More SSO discussion improvements in forum.wiki check-in: bc303c0e user: wyoung tags: trunk
19:30
More tweaks to the forum.wiki doc check-in: 5d75504a user: wyoung tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/forum.wiki.

154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170



171
172
173
174
175
176
177
178
179
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 capability bits 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 → 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.








|
|
|
|
|

|
|
|
|
>
>
>
|
|







154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
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 Fossil repository
separate from your project's main Fossil repository. A good reason to do
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 that is probably less well
known than it should be, which has been in the software since April of
2011: Admin &rarr; Login-Group, which allows one Fossil repository to
recognize users authorized on another Fossil repository.


<h3>Email Notification</h3>

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