-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
English fixes and minor code tidyup #175
Open
olipayne
wants to merge
2
commits into
heiglandreas:master
Choose a base branch
from
olipayne:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,9 +30,9 @@ | |
*/ | ||
?><div class="wrap"> | ||
<?php if (! extension_loaded('ldap')) : ?> | ||
<div class="error"><strong>Caveat:</strong> The LDAP-extension is not loaded! | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why did you remove the strong marking here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was more of a personal opinion, the alert is already inside a element so it seemed unnecessary to add extra emphasis on any text
|
||
Without that extension it is not possible to query an LDAP-Server! Please have a look | ||
at <a href="http://php.net/manual/install.php">the PHP-Installation page</a> | ||
<div class="error">The PHP LDAP Extension is not loaded! | ||
Without that extension it is not possible to query an LDAP Server. Please have a look | ||
at <a href="http://php.net/manual/install.php">the PHP Installation page</a> | ||
</div> | ||
<?php endif ?> | ||
<h2>AuthLDAP Options</h2> | ||
|
@@ -58,34 +58,34 @@ | |
</tr> | ||
<tr> | ||
<th> | ||
<label for="authLDAPDoNotOverwriteNonLdapUsers">Do not authenticate existing WordPress-Users</label> | ||
<label for="authLDAPDoNotOverwriteNonLdapUsers">Do not authenticate existing WordPress Users</label> | ||
</th> | ||
<td> | ||
<input type="checkbox" name="authLDAPDoNotOverwriteNonLdapUsers" id="authLDAPDoNotOverwriteNonLdapUsers" value="1"<?php echo $tDoNotOverwriteNonLdapUsers; ?>/> | ||
<p class="description"> | ||
Shall we prohibit authenticating already in WordPress created users using LDAP? If you enable this, LDAP-Users with the same user-ID | ||
as existing WordPress-Users can no longer take over the WordPress-Users account. This also means that LDAP-Users with the same User-ID as existing | ||
WordPress-Users will <strong>not</strong> be able to authenticate anymore! Accounts that have been taken over already will not be affected by this setting. | ||
Shall we prohibit authenticating already in WordPress created users using LDAP? If you enable this, LDAP Users with the same user ID | ||
as existing WordPress Users can no longer take over the WordPress User account. This also means that LDAP Users with the same User ID as existing | ||
WordPress Users will <strong>not</strong> be able to authenticate anymore! Accounts that have been taken over already will not be affected by this setting. | ||
</p> | ||
<p class="description">This should only be checked if you know what you are doing!</p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<th> | ||
<label for="authLDAPCachePW">Save entered passwords in the wordpress user table?</label> | ||
<label for="authLDAPCachePW">Save entered passwords in the WordPress User table?</label> | ||
</th> | ||
<td> | ||
<input type="checkbox" name="authLDAPCachePW" id="authLDAPCachePW" value="1"<?php echo $tPWChecked; ?>/> | ||
</td> | ||
</tr> | ||
<tr> | ||
<th> | ||
<label for="authLDAPGroupEnable">Map LDAP Groups to wordpress Roles?</label> | ||
<label for="authLDAPGroupEnable">Map LDAP Groups to WordPress Roles?</label> | ||
</th> | ||
<td> | ||
<input type="checkbox" name="authLDAPGroupEnable" id="authLDAPGroupEnable" value="1"<?php echo $tGroupChecked; ?>/> | ||
<p class="description"> | ||
Search LDAP for user's groups and map to Wordpress Roles. | ||
Search LDAP for User's groups and map to Wordpress Roles. | ||
</p> | ||
</td> | ||
</tr> | ||
|
@@ -99,34 +99,34 @@ | |
<label for="authLDAPURI">LDAP URI</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPURI" id="authLDAPURI" placeholder="LDAP-URI" | ||
<input type="text" name="authLDAPURI" id="authLDAPURI" placeholder="LDAP URI" | ||
class="regular-text" value="<?php echo $authLDAPURI; ?>"/> | ||
<p class="description"> | ||
The <abbr title="Uniform Ressource Identifier">URI</abbr> | ||
for connecting to the LDAP-Server. This usualy takes the form | ||
for connecting to the LDAP Server. This usualy takes the form | ||
<var><scheme>://<user>:<password>@<server>/<path></var> | ||
according to RFC 1738.</p> | ||
<p class="description"> | ||
In this case it schould be something like | ||
In this case it should be something like | ||
<var>ldap://uid=adminuser,dc=example,c=com:[email protected]/dc=basePath,dc=example,c=com</var>. | ||
</p> | ||
<p class="description"> | ||
If your LDAP accepts anonymous login, you can ommit the user and | ||
password-Part of the URI | ||
If your LDAP accepts anonymous login, you can omit the user and | ||
password part of the URI | ||
</p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<th> | ||
<label for="authLDAPURISeparator">LDAP URI-Separator</label> | ||
<label for="authLDAPURISeparator">LDAP URISeparator</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPURISeparator" id="authLDAPURISeparator" placeholder="LDAP-URI Separator" | ||
<input type="text" name="authLDAPURISeparator" id="authLDAPURISeparator" placeholder="LDAP URI Separator" | ||
class="regular-text" value="<?php echo $authLDAPURISeparator; ?>"/> | ||
<p class="description"> | ||
A separator that separates multiple LDAP-URIs from one another. | ||
You can use that feature to try to authenticate against multiple LDAP-Servers | ||
as long as they all have the same attribute-settings. The first LDAP-Server the user can | ||
A separator that separates multiple LDAP URIs from one another. | ||
You can use that feature to try to authenticate against multiple LDAP Servers | ||
as long as they all have the same attribute settings. The first LDAP Server the user can | ||
authenticate against will be used to handle the user. | ||
</td> | ||
</tr> | ||
|
@@ -193,8 +193,8 @@ | |
<input type="text" name="authLDAPSecName" id="authLDAPSecName" placeholder="" | ||
class="regular-text" value="<?php echo $authLDAPSecName; ?>" /> | ||
<p class="description"> | ||
If the above Name-Attribute only contains the First Name of the | ||
user you can here specify an Attribute that contains the second name. | ||
If the above Name Attribute only contains the First Name of the | ||
user you can here specify an Attribute that contains the Second Name. | ||
</p> | ||
<p class="description"> | ||
This field is empty by default | ||
|
@@ -203,14 +203,14 @@ | |
</tr> | ||
<tr> | ||
<th scope="row"> | ||
<label for="authLDAPUidAttr">User-ID Attribute</label> | ||
<label for="authLDAPUidAttr">User ID Attribute</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPUidAttr" id="authLDAPUidAttr" placeholder="uid" | ||
class="regular-text" value="<?php echo $authLDAPUidAttr; ?>" /> | ||
<p class="description"> | ||
Please give the Attribute, that is used to identify the user. This | ||
should be the same as you used in the above <em>Filter</em>-Option | ||
The Attribute that is used to identify the user. This | ||
should be the same as you used in the above <em>Filter</em> Option | ||
</p> | ||
<p class="description"> | ||
This field defaults to <strong>uid</strong> | ||
|
@@ -225,10 +225,10 @@ | |
<input type="text" name="authLDAPMailAttr" id="authLDAPMailAttr" placeholder="mail" | ||
class="regular-text" value="<?php echo $authLDAPMailAttr; ?>" /> | ||
<p class="description"> | ||
Which Attribute holds the eMail-Address of the user? | ||
The Attribute which defines the email address of the user | ||
</p> | ||
<p class="description"> | ||
If more than one eMail-Address are stored in the LDAP, only the first given is used | ||
If more than one email address is stored, only the first given is used | ||
</p> | ||
<p class="description"> | ||
This field defaults to <strong>mail</strong> | ||
|
@@ -237,7 +237,7 @@ | |
</tr> | ||
<tr> | ||
<th scope="row"> | ||
<label for="authLDAPWebAttr">Web-Attribute</label> | ||
<label for="authLDAPWebAttr">Web Attribute</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPWebAttr" id="authLDAPWebAttr" placeholder="" | ||
|
@@ -257,11 +257,11 @@ | |
</th> | ||
<td> | ||
<select name="authLDAPDefaultRole" id="authLDAPDefaultRole"> | ||
<option value="" <?php echo ( $authLDAPDefaultRole == '' ? 'selected="selected"' : '' ); ?>> | ||
<option value="" <?php echo($authLDAPDefaultRole == '' ? 'selected="selected"' : ''); ?>> | ||
None (deny access) | ||
</option> | ||
<?php foreach ($roles->get_names() as $group => $vals) : ?> | ||
<option value="<?php echo $group; ?>" <?php echo ( $authLDAPDefaultRole == $group ? 'selected="selected"' : '' ); ?>> | ||
<option value="<?php echo $group; ?>" <?php echo($authLDAPDefaultRole == $group ? 'selected="selected"' : ''); ?>> | ||
<?php echo $vals; ?> | ||
</option> | ||
<?php endforeach; ?> | ||
|
@@ -302,22 +302,22 @@ | |
<input type="text" name="authLDAPGroupBase" id="authLDAPGroupBase" placeholder="" | ||
class="regular-text" value="<?php echo $authLDAPGroupBase; ?>" /> | ||
<p class="description"> | ||
This is the base dn to lookup groups. | ||
This is the Base DN to lookup groups. | ||
</p> | ||
<p class="description"> | ||
If empty the base dn of the LDAP URI will be used | ||
If empty the Base DN of the LDAP URI will be used | ||
</p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<th scope="row"> | ||
<label for="authLDAPGroupAttr">Group-Attribute</label> | ||
<label for="authLDAPGroupAttr">Group Attribute</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPGroupAttr" id="authLDAPGroupAttr" placeholder="gidNumber" | ||
class="regular-text" value="<?php echo $authLDAPGroupAttr; ?>" /> | ||
<p class="description"> | ||
This is the attribute that defines the Group-ID that can be matched | ||
This is the Attribute that defines the Group ID that can be matched | ||
against the Groups defined further down | ||
</p> | ||
<p class="description"> | ||
|
@@ -327,15 +327,15 @@ | |
</tr> | ||
<tr> | ||
<th scope="row"> | ||
<label for="authLDAPGroupSeparator">Group-Separator</label> | ||
<label for="authLDAPGroupSeparator">Group Separator</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPGroupSeparator" id="authLDAPGroupSeparator" placeholder="," | ||
class="regular-text" value="<?php echo $authLDAPGroupSeparator; ?>" /> | ||
<p class="description"> | ||
This attribute defines the separator used for the Group-IDs listed in the | ||
Groups defined further down. This is useful if the value of Group-Attribute | ||
listed above can contain a comma (for example, when using the memberof attribute) | ||
This attribute defines the separator used for the Group IDs listed in the | ||
Groups defined further down. This is useful if the value of Group Attribute | ||
listed above can contain a comma (for example, when using the memberOf attribute) | ||
</p> | ||
<p class="description"> | ||
This field defaults to <strong>, (comma)</strong> | ||
|
@@ -344,24 +344,24 @@ | |
</tr> | ||
<tr> | ||
<th scope="row"> | ||
<label for="authLDAPGroupFilter">Group-Filter</label> | ||
<label for="authLDAPGroupFilter">Group Filter</label> | ||
</th> | ||
<td> | ||
<input type="text" name="authLDAPGroupFilter" id="authLDAPGroupFilter" | ||
placeholder="(&(objectClass=posixGroup)(memberUid=%s))" | ||
class="regular-text" value="<?php echo $authLDAPGroupFilter; ?>" /> | ||
<p class="description"> | ||
Here you can add the filter for selecting groups for ther | ||
currentlly logged in user | ||
Here you can add the filter for selecting groups for the | ||
currently logged in user | ||
</p> | ||
<p class="description"> | ||
The Filter should contain the string <code>%s</code> which will be replaced by | ||
the login-name of the currently logged in user | ||
the login name of the currently logged in user | ||
</p> | ||
<p class="description"> | ||
Alternatively the string <code>%dn%</code> will be replaced by the | ||
DN of the currently logged in user. This can be helpfull if | ||
group-memberships are defined with DNs rather than UIDs | ||
DN of the currently logged in user. This can be helpful if | ||
group memberships are defined with DNs rather than UIDs | ||
</p> | ||
<p class="description">This field defaults to | ||
<strong>(&(objectClass=posixGroup)(memberUid=%s))</strong> | ||
|
@@ -371,7 +371,7 @@ | |
</table> | ||
</fieldset> | ||
|
||
<h3 class="title">Role - group mapping</h3> | ||
<h3 class="title">Role - Group Mapping</h3> | ||
<fieldset class="options"> | ||
<table class="form-table"> | ||
<?php | ||
|
@@ -386,8 +386,8 @@ | |
<td> | ||
<input type="text" name="authLDAPGroups[<?php echo $group; ?>]" id="authLDAPGroups[<?php echo $group; ?>]" | ||
value="<?php echo $aGroup; ?>" /> | ||
<p class="description">What LDAP-Groups shall be matched to the <?php echo $vals; ?>-Role?</p> | ||
<p class="description">Please provide a coma-separated list of values</p> | ||
<p class="description">What LDAP Groups should be matched to the <?php echo $vals; ?> Role?</p> | ||
<p class="description">Please provide a comma-separated list of values</p> | ||
<p class="description">This field is empty by default</p> | ||
</td> | ||
</tr> | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This wording was used deliberately as the library tries multiple binds and none of these is successful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I misunderstood the context, 'No bind successful' is a viable alternative :)