Publ supports the use of Authl, an authentication wrapper library, to make it easier to control access to private posts. By configuring a few values in the application configuration and setting up some user groups, you can get fine-grained control over who can see specific posts.
The main things to pay attention to are as follows:
app.secret_key controls the signing of the authentication tokens. Essentially, it needs to be kept secret, to prevent others from gaining access that they shouldn’t have.
By default this is set randomly every time the application starts, which is secure but it means that any time the server restarts, everyone will be logged out. So, you’ll probably want to set this to a secret value that gets set with an environment variable or the like; for example, after the
app is created:
Alternately, you might want to automatically generate the secret key as a local file:
This is a key-value dictionary that is sent along to Authl’s
from_config settings. See the Authl documentation for the most up-to-date configuration flags; here are some that you are likely to want to use:
- SSL options:
AUTH_FORCE_HTTPS: set to True if logins should all go over HTTPS instead of HTTP (highly recommended!)
- Email options:
SMTP_HOST: the email host (required; usually
SMTP_PORT: the email port (required; usually
SMTP_USE_SSL: whether to use SSL for the SMTP connection (not necessary for
localhostbut highly recommended for anything else)
EMAIL_FROM: the From: address to use when sending an email (required)
EMAIL_SUBJECT: the Subject: to use for a login email (required)
EMAIL_LOGIN_TIMEOUT: How long (in seconds) the user has to follow the login link
- IndieAuth options:
INDIEAUTH_CLIENT_ID: The client ID to send to the remote IndieAuth endpoint (required)1
- Fediverse (e.g. Mastodon) options:
FEDIVERSE_NAME: the name of your website (required)
FEDIVERSE_HOMEPAGE: your website’s main URL (recommended)
TWITTER_CLIENT_SECRET: a Twitter application client key and secret
Note that for safety’s sake these should be read from environment variables, rather than checked in to code.
In order to get these you need to go to the Twitter developer portal and register your website as an application. If asked for app usage, simply say “To provide Login with Twitter functionality to my website” or similar.
You will also need to register your Twitter login callback URLs; this will probably be something like
Test handler options:
TEST_ENABLED: whether to enable the
test:test handler. Don’t do this.
This is the filename of a file where you configure access to users and groups. The format is based on a common configuration file format; see the
user.cfg format for more information.
This configuration setting specifies which user group will have administrative access; by default this is set to
admin. Thus, in the above example, the user who logs in as
http://example.com/me will be a member of that group.
You can also set this configuration option to a specific identity.
Members of the administrative group will always be able to see all entries, and will also have access to the administrative functions of the site (such as being able to see the user log).
See the Auth: header.