refeed/trunk/ACCOUNTS.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
        <title>Reblog User Accounts/Authentication</title> 
        <link rel="stylesheet" href="softwarestyle.css" type="text/css" />
</head>
<body>
    <h1>Reblog User Accounts/Authentication</h1>
    <p>$Revision: 1.3 $</p>
    <div id="contents">
    <a name="#overview"></a>
    <h3>Overview</h3>
    <p>
    By default, the feed-reading software component of reBlog, called reFeed, is a
    single-user application.  Its database allows for multiple users to each maintain
    their own set of input feeds and published posts, but there is no account 
    creation/management system, or method to authenticate different users.
    </p>

    <p>
    However, in reBlog 2.1 beta, we have enabled multiple user accounts within one 
    reFeed installation. The account management and authentication is piggybacked on 
    other systems that refeed already interfaces with in different ways.
    </p>


    <a name="#overview"></a>
    <h3>reFeed Built-in Auth</h3>
    <p>
    By default, reFeed does not authenticate or restrict access.  By setting values for
    the <code>REBLOG_HTTPAUTH_NAME</code> and <code>REBLOG_HTTPAUTH_PASS</code> settings,
    as described in the <a href="INSTALL.html">install instructions</a>, you can enable simple
    Basic HTTP Authentication for a single user.
    </p>
    
    <a name="#piggyback"></a>
    <h3>Blog System Accounts/Auth Piggybacking</h3>
    <p>
    As mentioned, reFeed can now work with multiple users when installed within the context
    of other account-managing systems, as described below.
    </p>


    <a name="#mt"></a>
    <h2>Movable Type</h2>
    <p>
    Install reFeed normally, but place the whole installation in the same directory as 
    your <code>mt.cgi</code>, so that you would access reFeed at:
    http://example.com/path/to/mt/refeed.  Then set <code>REBLOG_AUTH_TYPE</code>
    to <code>MT</code> in <code>config.php</code>.  reFeed will then authenticate
    against the Movable Type cookie and database, giving each user in your Movable Type
    installation their own reFeed account.  For this to work, refeed must be configured to use the
    same MySQL database as Movable Type.
    </p>


    <a name="#wp"></a>
    <h2>WordPress</h2>
    <p>
    Do the same thing as for Movable Type, placing refeed inside your WordPress installation,
    and set <code>REBLOG_AUTH_TYPE</code> to <code>MT</code> in <code>config.php</code>.
    Then all of your WordPress users will have their own refeed accounts.  
    For this to work, refeed must be configured to use the
    same MySQL database as WordPress.
    </p>


    <a name="#drupal"></a>
    <h3>Drupal</h3>
    <p>
    We are also working on a tighter integration of reFeed with Drupal, but this is not quite
    ready for release.  Get in touch with us if you want to chat about it.    
    </p>

    </div>
</body>
</html>
1	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3	<html xmlns="http://www.w3.org/1999/xhtml">
4	<head>
5	<title>Reblog User Accounts/Authentication</title>
6	<link rel="stylesheet" href="softwarestyle.css" type="text/css" />
7	</head>
8	<body>
9	<h1>Reblog User Accounts/Authentication</h1>
10	<p>$Revision: 1.3 $</p>
11	<div id="contents">
12	<a name="#overview"></a>
13	<h3>Overview</h3>
14	<p>
15	By default, the feed-reading software component of reBlog, called reFeed, is a
16	single-user application. Its database allows for multiple users to each maintain
17	their own set of input feeds and published posts, but there is no account
18	creation/management system, or method to authenticate different users.
19	</p>
20
21	<p>
22	However, in reBlog 2.1 beta, we have enabled multiple user accounts within one
23	reFeed installation. The account management and authentication is piggybacked on
24	other systems that refeed already interfaces with in different ways.
25	</p>
26
27
28	<a name="#overview"></a>
29	<h3>reFeed Built-in Auth</h3>
30	<p>
31	By default, reFeed does not authenticate or restrict access. By setting values for
32	the <code>REBLOG_HTTPAUTH_NAME</code> and <code>REBLOG_HTTPAUTH_PASS</code> settings,
33	as described in the <a href="INSTALL.html">install instructions</a>, you can enable simple
34	Basic HTTP Authentication for a single user.
35	</p>
36
37	<a name="#piggyback"></a>
38	<h3>Blog System Accounts/Auth Piggybacking</h3>
39	<p>
40	As mentioned, reFeed can now work with multiple users when installed within the context
41	of other account-managing systems, as described below.
42	</p>
43
44
45	<a name="#mt"></a>
46	<h2>Movable Type</h2>
47	<p>
48	Install reFeed normally, but place the whole installation in the same directory as
49	your <code>mt.cgi</code>, so that you would access reFeed at:
50	http://example.com/path/to/mt/refeed. Then set <code>REBLOG_AUTH_TYPE</code>
51	to <code>MT</code> in <code>config.php</code>. reFeed will then authenticate
52	against the Movable Type cookie and database, giving each user in your Movable Type
53	installation their own reFeed account. For this to work, refeed must be configured to use the
54	same MySQL database as Movable Type.
55	</p>
56
57
58	<a name="#wp"></a>
59	<h2>WordPress</h2>
60	<p>
61	Do the same thing as for Movable Type, placing refeed inside your WordPress installation,
62	and set <code>REBLOG_AUTH_TYPE</code> to <code>MT</code> in <code>config.php</code>.
63	Then all of your WordPress users will have their own refeed accounts.
64	For this to work, refeed must be configured to use the
65	same MySQL database as WordPress.
66	</p>
67
68
69	<a name="#drupal"></a>
70	<h3>Drupal</h3>
71	<p>
72	We are also working on a tighter integration of reFeed with Drupal, but this is not quite
73	ready for release. Get in touch with us if you want to chat about it.
74	</p>
75
76	</div>
77	</body>
78	</html>