[Rt-commit] rt branch, 4.4/update-auth-documentation, repushed

Jim Brandt jbrandt at bestpractical.com
Fri May 13 14:39:17 EDT 2016


The branch 4.4/update-auth-documentation was deleted and repushed:
       was c0edb38c8e0a7573b69212490cd7df4b4496823e
       now 707e1014b8699c40788032f1786f16be19fb9117

1:  c0edb38 ! 1:  707e101 Update authentication documentation
    @@ -21,13 +21,14 @@
     -authentication.
     +Starting with RT 4.4, both of these options are supported by RT out of the
     +box, activated using different configuration options. The first is supported
    -+by the F<lib/RT/Authen/ExternalAuth> module. The second is activated using
    ++by the L<RT::Authen::ExternalAuth> module. The second is activated using
     +the configuration option C<$WebRemoteUserAuth> along with some related
     +options. These two types may be used independently or together, and both
     +can fallback to RT's internal authentication.
     +
     +If you are running a version of RT earlier than 4.4, you can install
    -+L<RT::Authen::ExternalAuth> as an extension.
    ++L<RT::Authen::ExternalAuth|https://metacpan.org/pod/RT::Authen::ExternalAuth>
    ++as an extension.
      
      No matter what type of external authentication you use, RT still maintains user
      records in its database that correspond to your external source.  This is
    @@ -36,7 +37,7 @@
      additional information from your external source.  Synchronization of users,
      user data, and groups is provided by an extension named
     -L</RT::Extension::LDAPImport>.  It uses an external LDAP source, such an
    -+F<lib/RT/Extension/LDAPImport>.  It uses an external LDAP source, such an
    ++L<RT::LDAPImport>.  It uses an external LDAP source, such an
      OpenLDAP or Active Directory server, as the authoritative repository and keeps
      RT up to date accordingly.  This can be used in tandem with any of the external
      authentication options as it does not provide any authentication itself.
    @@ -46,8 +47,8 @@
      In order to keep user data in sync, this type of external auth is almost always
     -used in combination with one or both of L</RT::Authen::ExternalAuth> and
     -L</RT::Extension::LDAPImport>.
    -+used in combination with one or both of F<lib/RT/Authen/ExternalAuth> and
    -+F<lib/RT/Extension/LDAPImport>.
    ++used in combination with one or both of L<RT::Authen::ExternalAuth> and
    ++L<RT::LDAPImport>.
      
     -=head3 Apache configuration
     +=head3 Apache Configuration
    @@ -89,7 +90,7 @@
      =head2 Via RT's login form, aka RT::Authen::ExternalAuth
      
     -L<RT::Authen::ExternalAuth> is an RT extension which provides authentication
    -+F<lib/RT/Authen/ExternalAuth> provides authentication
    ++L<RT::Authen::ExternalAuth> provides authentication
      B<using> RT's login form.  It can be configured to talk to an LDAP source (such
      as Active Directory), an external database, or an SSO cookie.
      
    @@ -97,19 +98,15 @@
     -is the use of the RT login form and what part of the system talks to your
     -authentication source (your web server vs. RT itself).
     +The key difference between C<$WebRemoteUserAuth> and
    -+F<lib/RT/Authen/ExternalAuth> is the use of the RT login form and what
    ++L<RT::Authen::ExternalAuth> is the use of the RT login form and what
     +part of the system talks to your authentication source (your web
     +server vs. RT itself).
     +
     +As noted above, for versions of RT before 4.4, you can install
    -+L<RT::Authen::ExternalAuth> as an extension.
    ++L<RT::Authen::ExternalAuth|https://metacpan.org/pod/RT::Authen::ExternalAuth>
    ++as an extension.
      
      =head3 Info mode and Authentication mode
    - 
    --There are two modes of operation in L<RT::Authen::ExternalAuth>: info and auth.
    -+There are two modes of operation in F<lib/RT/Authen/ExternalAuth>: info and auth.
    - Usually you want to configure both so that successfully authenticated users
    - also get their information pulled and updated from your external source.
      
     @@
      
    @@ -121,14 +118,14 @@
     -than L<RT::Authen::ExternalAuth> (which only updates upon login and doesn't
     -handle groups).  It may be used with either of RT's external authentication
     -sources, or on it's own.
    -+F<lib/RT/Extension/LDAPImport> provides no authentication, but is worth
    ++L<RT::LDAPImport> provides no authentication, but
     +is useful alongside authentication because it provides user data and group
     +member synchronization from any LDAP source into RT.  It provides a similar
    -+but more complete sync solution than C<RT::Authen::ExternalAuth> (which
    ++but more complete sync solution than L<RT::Authen::ExternalAuth> (which
     +only updates upon login and doesn't handle groups).  It may be used with
     +either of RT's external authentication sources, or on it's own.
     +
    -+Starting with RT 4.4, F<lib/RT/Extension/LDAPImport> is part of RT. For
    ++Starting with RT 4.4, L<RT::LDAPImport> is part of RT. For
     +earlier versions of RT, you can install L<RT::Extension::LDAPImport> as
     +an extension.
     



More information about the rt-commit mailing list