The authLdap plugin is installed on all Kingdom WordPress sites. This plugin allows local Officers to log in to your WordPress Site and post to it if they are given access. This will make it easier for you to delegate content creation and maintenance to others in your branch or greater office. Holders of designated offices will be able to log in with their designated roles. Anyone who attempts to log in without being configured in authLDAP will not be given access.

Configuration:

Under the ‘Settings’ section of WordPress you’ll find a page of settings for AuthLdap. Most of these settings should be configured already when the Webministry installed the plugin. However, there are some things to know.

• The section titled “Role-group Mapping” is where the list of authorized officers are entered, and which roles they will have. See below for a brief primer on WordPress Roles. Only warranted webministers should be entered in the Administrator section. This is configured by default to include the local webminister and the Kingdom Webministry Helpdesk team.
• Optionally add other offices into the other roles. e.g., seneschal@[branch].eastkingdom.org as Editor, or chronicler@[branch].eastkingdom.org as Author.
• Be sure to enter the address of the office, not the address of the person holding the office. When the office changes hands, the new officer will automatically have the access specified, and the old officer will no longer be able to log in.

Now that the plugin is configured and all the settings are saved, any member attached to one of the entered offices can log in with their member number as their username and their EK account password. Once logged in they can be set as the author of a page, granting them the ability to edit that page. You can also use all of the other ownership and permission options available in WordPress. You will see them in WordPress under their name and member number rather than their office address, as they are still logging in as themselves, and confirmed to have access by their officer role.

Officer changes

When an office is handed off to a new member and you’ve completed making that change in FusionDirectory, the new office holder will be able to log in automatically with no adjustments needed. The old officer will lose any WordPress roles associated with the office. If the old officer no longer holds any office, they will be unable to log in to WordPress at all. They will still appear in the WordPress users table, so you will likely want to manually remove them. You will also need to reassign any pages or posts owned by the old officer to the new one.

A brief primer on WordPress Roles

• Administrator – Full access, can manage the site, its contents, plugins, themes, users, etc.
• Editor – Can create and post content, and can edit other people’s content.
• Author – Can create and post content, can edit their own content.
• Contributor – Can create content, but an Editor or Administrator must publish it.
• Subscriber – Can log in. Cannot create content. Only useful if you restrict access to functions (like commenting) or parts of the site to those who can log in.