ExternalAuthentication - Revision history

Admin: 9 revisions imported

2016-04-06T20:08:59Z

9 revisions imported

← Older revision		Revision as of 16:08, 6 April 2016
(No difference)

209.147.96.204: /* 4. LDAPS */

2013-06-05T15:31:34Z

4. LDAPS

← Older revision		Revision as of 11:31, 5 June 2013
Line 23:		Line 23:
	== 4. LDAPS ==		== 4. LDAPS ==

	RT::Authen::ExternalAuth supports LDAPS out of the box. Simply specify a server of "ldaps://example.com". You'll also need to make sure that the Net::LDAPS Perl module is installed, either via your distribution's package manager or the `cpan` command. ~~oleg::perl~~		RT::Authen::ExternalAuth supports LDAPS out of the box. Simply specify a server of "ldaps://example.com". You'll also need to make sure that the Net::LDAPS Perl module is installed, either via your distribution's package manager or the `cpan` command.

209.147.96.204: /* 4. LDAPS */

2013-06-05T15:31:16Z

4. LDAPS

New page

= External Authentication =

External Authentication of users against LDAP, SQL and other data sources can be achieved easily in one of three ways.

== 1. Apache Authentication ==

You can configure RT to listen to Apache for an authenticated user. This a flexible but featureless way to authenticate and is detailed in the [[WebExternalAuth]] page. You simply configure Apache to restrict authentication via pluggable modules (such as mod_ldap for LDAP authentication).

== 2. RT::Authen::ExternalAuth ==

Available via CPAN (cpan -i RT::Authen::[[ExternalAuth]]), [[ExternalAuth]] is an [[RTx]]-style extension to RT that allows authentication and information lookup via any number of external sources, currently limited to LDAP and DBI-supported information services which includes Microsoft Active Directory, [[OpenLDAP]], [[MySQL]], MSSQL, Oracle, Flat files, and many more.

Authentication and information lookup can be configured separately and as many sources as required can be specified which will all be checked in order until a successful result is encountered.

Single Sign-On with other web code via browser cookies is also supported.

More details are available at [[ExternalAuth]].

== 3. Manual Overlays ==

You can create & customise your own authentication mechanisms by modifying one of the above methods to suit your needs, or overlaying RT's own files with local modifications.

== 4. LDAPS ==

RT::Authen::ExternalAuth supports LDAPS out of the box. Simply specify a server of "ldaps://example.com". You'll also need to make sure that the Net::LDAPS Perl module is installed, either via your distribution's package manager or the `cpan` command. oleg::perl

193.206.99.132: /* 2. RT::Authen::ExternalAuth */

2013-05-27T14:00:32Z

2. RT::Authen::ExternalAuth

← Older revision		Revision as of 10:00, 27 May 2013
Line 11:		Line 11:
	Available via CPAN (cpan -i RT::Authen::[[ExternalAuth]]), [[ExternalAuth]] is an [[RTx]]-style extension to RT that allows authentication and information lookup via any number of external sources, currently limited to LDAP and DBI-supported information services which includes Microsoft Active Directory, [[OpenLDAP]], [[MySQL]], MSSQL, Oracle, Flat files, and many more.		Available via CPAN (cpan -i RT::Authen::[[ExternalAuth]]), [[ExternalAuth]] is an [[RTx]]-style extension to RT that allows authentication and information lookup via any number of external sources, currently limited to LDAP and DBI-supported information services which includes Microsoft Active Directory, [[OpenLDAP]], [[MySQL]], MSSQL, Oracle, Flat files, and many more.

	Authentication and information lookup can be ~~configure~~ separately and as many sources as required can be specified which will all be checked in order until a successful result is encountered.		Authentication and information lookup can be configured separately and as many sources as required can be specified which will all be checked in order until a successful result is encountered.

	Single Sign-On with other web code via browser cookies is also supported.		Single Sign-On with other web code via browser cookies is also supported.

213.151.88.252: add section on LDAPS

2013-05-27T06:24:00Z

add section on LDAPS

← Older revision		Revision as of 02:24, 27 May 2013
Line 20:		Line 20:

	You can create & customise your own authentication mechanisms by modifying one of the above methods to suit your needs, or overlaying RT's own files with local modifications.		You can create & customise your own authentication mechanisms by modifying one of the above methods to suit your needs, or overlaying RT's own files with local modifications.

			== 4. LDAPS ==

			Although RT::Authen::ExternalAuth does not support LDAPS out of the box, this is easily fixed. For a description of how one guy got LDAPS working under openSUSE 12.3 with Request Tracker 4.0.13 and RT::Authen::ExternalAuth 0.12, see the blog entry [http://smithfarm-thebrain.blogspot.cz/2013/05/request-tracker-set-up-external.html Request Tracker: set up external authentication via LDAPS]

130.235.93.68: /* 1. Apache Authentication */

2013-02-01T10:12:38Z

1. Apache Authentication

← Older revision		Revision as of 06:12, 1 February 2013
Line 5:		Line 5:
	== 1. Apache Authentication ==		== 1. Apache Authentication ==

	You can configure RT to listen to Apache for an authenticated user. This a flexible but featureless way to authenticate and is detailed in the [[WebExternalAuth]] page. You ~~simple~~ configure Apache to restrict authentication via pluggable modules (such as mod_ldap for LDAP authentication).		You can configure RT to listen to Apache for an authenticated user. This a flexible but featureless way to authenticate and is detailed in the [[WebExternalAuth]] page. You simply configure Apache to restrict authentication via pluggable modules (such as mod_ldap for LDAP authentication).

	== 2. RT::Authen::ExternalAuth ==		== 2. RT::Authen::ExternalAuth ==

116.197.178.83: /* 3. Manual Overlays */

2011-03-09T11:28:40Z

3. Manual Overlays

New page

= External Authentication =

External Authentication of users against LDAP, SQL and other data sources can be achieved easily in one of three ways.

== 1. Apache Authentication ==

You can configure RT to listen to Apache for an authenticated user. This a flexible but featureless way to authenticate and is detailed in the [[WebExternalAuth]] page. You simple configure Apache to restrict authentication via pluggable modules (such as mod_ldap for LDAP authentication).

== 2. RT::Authen::ExternalAuth ==

Available via CPAN (cpan -i RT::Authen::[[ExternalAuth]]), [[ExternalAuth]] is an [[RTx]]-style extension to RT that allows authentication and information lookup via any number of external sources, currently limited to LDAP and DBI-supported information services which includes Microsoft Active Directory, [[OpenLDAP]], [[MySQL]], MSSQL, Oracle, Flat files, and many more.

Authentication and information lookup can be configure separately and as many sources as required can be specified which will all be checked in order until a successful result is encountered.

Single Sign-On with other web code via browser cookies is also supported.

More details are available at [[ExternalAuth]].

== 3. Manual Overlays ==

You can create & customise your own authentication mechanisms by modifying one of the above methods to suit your needs, or overlaying RT's own files with local modifications.