[Bps-public-commit] rt-authen-externalauth branch, master, updated. 0.13-16-g17ee221

[Thomas Sibley]

The branch, master has been updated
       via  17ee221285c4a856bc0930a44b4699d8d866e7f0 (commit)
       via  94370064f8e351338c946195fcdb8f0adebf0001 (commit)
      from  3a1829d2d6e7c569b010b10f1b1d8ed519912d36 (commit)

Summary of changes:
 etc/RT_SiteConfig.pm          |  7 +++----
 lib/RT/Authen/ExternalAuth.pm | 14 +++++++-------
 2 files changed, 10 insertions(+), 11 deletions(-)

- Log -----------------------------------------------------------------
commit 94370064f8e351338c946195fcdb8f0adebf0001
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Wed May 22 14:13:45 2013 -0700

    Remove a second "However, ..." for readability

diff --git a/etc/RT_SiteConfig.pm b/etc/RT_SiteConfig.pm
index ec906c4..f8fe8fb 100644
--- a/etc/RT_SiteConfig.pm
+++ b/etc/RT_SiteConfig.pm
@@ -183,10 +183,9 @@ If a new user sent an email to RT from an email alias, the search
 would match on the alias and that alias would be set as the user's
 EmailAddress in RT when the new account is created.
 
-However, if a user with an existing RT account, with EmailAddress set
-to the C<mail> address, sent mail from C<alias>, it would
-still match. However, the user's EmailAddress in RT would
-remain the primary C<mail> address.
+However, if a user with an existing RT account with EmailAddress set to the
+C<mail> address, sent mail from C<alias>, it would still match. The user's
+EmailAddress in RT would remain the primary C<mail> address.
 
 This feature is useful for LDAP configurations where users have
 a primary institutional email address, but might also use aliases from

commit 17ee221285c4a856bc0930a44b4699d8d866e7f0
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Wed May 22 14:14:09 2013 -0700

    Outdent non-code and indent code
    
    Two nits noticed while skimming.

diff --git a/lib/RT/Authen/ExternalAuth.pm b/lib/RT/Authen/ExternalAuth.pm
index fba935d..2194dee 100644
--- a/lib/RT/Authen/ExternalAuth.pm
+++ b/lib/RT/Authen/ExternalAuth.pm
@@ -4,16 +4,16 @@ our $VERSION = '0.13';
 
 =head1 NAME
 
-  RT::Authen::ExternalAuth - RT Authentication using External Sources
+RT::Authen::ExternalAuth - RT Authentication using External Sources
 
 =head1 DESCRIPTION
 
-  A complete package for adding external authentication mechanisms
-  to RT. It currently supports LDAP via Net::LDAP and External Database
-  authentication for any database with an installed DBI driver.
+A complete package for adding external authentication mechanisms
+to RT. It currently supports LDAP via Net::LDAP and External Database
+authentication for any database with an installed DBI driver.
 
-  It also allows for authenticating cookie information against an
-  external database through the use of the RT-Authen-CookieAuth extension.
+It also allows for authenticating cookie information against an
+external database through the use of the RT-Authen-CookieAuth extension.
 
 =head1 UPGRADING
 
@@ -98,7 +98,7 @@ If you are using RT 3.8.x, you need to enable this
 module by adding RT::Authen::ExternalAuth to your
 @Plugins configuration:
 
-Set( @Plugins, qw(RT::Authen::ExternalAuth) );
+    Set( @Plugins, qw(RT::Authen::ExternalAuth) );
 
 If you already have a @Plugins line, add RT::Authen::ExternalAuth to the
 existing list.  Adding a second @Plugins line will cause interesting

-----------------------------------------------------------------------