Difference between revisions of "Talk:Main Page"

Revision as of 16:48, 6 March 2008

Found on the TWiki:

As far as I can tell, the "complete" set of documentation for WeBWorK should consist of the following:

a description of webwork for the student, professor, and administrator
system requirements (in the installation manual)
installation instructions (installation manual)
configuration instructions
- basic configuration is in installation manual
- a comprehensive list of course environment variables is now in the comments of global.conf and database.conf, but needs to be made accessible. convert to POD?
- Constants.pm has POD docs, but they have to get put on the wiki
- the NETPBM stuff is in the installation manual (but really should go away!!!)
task-oriented usage instructions
- admin tasks (like course creation)
  - course admin tasks
- instructor tasks
- student tasks
command line script documentation
library reference (this is/will be POD)
pg language reference
- basics
- cookbook techniques
- standard macro packages and modules (some of this exists in POD form on Frontier site)
- extending pg
how to get support
contributing to the webwork project (patches, donations, etc)

(this list originally from Message-ID: <20031001034004.A92569@gate.math.rochester.edu>)

-- Main.SamHathaway - 10 Nov 2003

Found on the TWiki:

There is quite a bit of documentation written for WebWorK 1.x. Some of it is still applicable to WeBWorK 2, including:

-- Main.SamHathaway - 24 Aug 2004

Moodle database is used, a bunch of boondoggle to connect it to MediaWiki (sso in Moodle and AuthMoodle.php (which sucks) in MW.
MediaWiki fails! when trying to create MW user record on first login.

Primary user database is on MediaWiki (with passwords in MW usesalt format)
Moodle creates user record from MW data
- Can I get Moodle to require the additional required fields that it doesn't get from MW?
Moodle authenticates against MW password
- any issue with usesalt?
Do this with Moodle's built-in "external database authentication"

— Sam 15:08, 6 March 2008 (EST)

External database authentication ALMOST supports this
passtype is used to transform the password string before checking it against the DB.
Could add a type for usesalt MD5, but it would have to be a change to the EXECUTE line, since it needs to grab the MW user_id field to use in the hashing.

@@ Line 49: / Line 49: @@
 == Fixing authentication ==
-;Right now:
+=== Right now ===
-* Moodle database is used, a bunch of boondoggle to connect it to MediaWiki.
+* Moodle database is used, a bunch of boondoggle to connect it to MediaWiki (<code>sso</code> in Moodle and <code>AuthMoodle.php</code> (which sucks) in MW.
 * MediaWiki '''fails!''' when trying to create MW user record on first login.
-;I want:
+=== I want ===
-* Primary user database is on MediaWiki (with passwords in MW double-salted format)
+* Primary user database is on MediaWiki (with passwords in MW <code>usesalt</code> format)
 * Moodle creates user record from MW data
 ** Can I get Moodle to require the additional required fields that it doesn't get from MW?
 * Moodle authenticates against MW password
-** any issue with double-salted hashes?
+** any issue with <code>usesalt</code>?
 * Do this with Moodle's built-in "external database authentication"
 {{--}} [[User:Sam|Sam]] 15:08, 6 March 2008 (EST)
+=== Notes ===
+* External database authentication ALMOST supports this
+* <code>passtype</code> is used to transform the password string before checking it against the DB.
+* Could add a type for <code>usesalt</code> MD5, but it would have to be a change to the <code>EXECUTE</code> line, since it needs to grab the MW <code>user_id</code> field to use in the hashing.