github
Advanced Search
  • Home
  • Pricing and Signup
  • Explore GitHub
  • Blog
  • Login

saju / mod_auth_remote

  • Admin
  • Watch Unwatch
  • Fork
  • Your Fork
  • Pull Request
  • Download Source
    • 3
    • 2
  • Source
  • Commits
  • Network (2)
  • Issues (0)
  • Downloads (1)
  • Wiki (2)
  • Graphs
  • Branch: ssl_backend

click here to add a description

click here to add a homepage

  • Branches (4)
    • 0,2-beta
    • chocolate_cookies
    • master
    • ssl_backend ✓
  • Tags (1)
    • 0.2-beta
Sending Request…
Enable Donations

Pledgie Donations

Once activated, we'll place the following badge in your repository's detail box:
Pledgie_example
This service is courtesy of Pledgie.

Remote authentication module for Apache httpd 2.2 — Read more

  cancel

  cancel
  • Private
  • Read-Only
  • HTTP Read-Only

This URL has Read+Write access

alloc a buffer of exactly 20 bytes 
David Mugnai (author)
Tue Sep 22 01:25:05 -0700 2009
saju (committer)
Wed Sep 23 00:53:25 -0700 2009
commit  733010a2381ac5e3301e848ea3c3ef55b53df5c3
tree    982b65c2de29c9adff1647674f7a34bde3dc4152
parent  29efcc3f2b903c1a70aae80c174547e6d638492c
mod_auth_remote /
name age
history
message
file README Loading commit data...
directory docs/
directory src/
README
             Mod_Auth_Remote - remote authentication module for apache 2.2
             Author:  Saju Pillai (saju.pillai@gmail.com)
                  

  mod_auth_remote is as an authentication provider. mod_auth_remote is configured with an
  authentication server url. The authentication server url is an application usually hosted
  by another webserver or webservice which is responsible for the actual authentication of
  users.

  mod_auth_remote accepts HTTP BASIC authentication requests and proxies a HTTP BASIC 
  Auth 'HEAD' request to the authentication server url on the local requests behalf.
  The authentication server may allow or decline authentication based on it's policy. If the 
  response from the authentication server is a SUCCESS code (2XX), mod_auth_remote will grant 
  AUTHENTICATION on the local server. For all other responses mod_auth_remote will deny local 
  AUTHENTICATION.


  Using mod_auth_remote gives you the following advantages

  * Simple way to implement Single-Signon. Same set of credentials can be used by 
    many applications/webservers.

  * No need to replicate your authentication framework to all your applications
      -- No need to punch holes through your firewall for sql access or ldap access as part of 
         your authentication setup.
      -- Authentication server need not be publicly accessible to actual clients
      -- Tweak your authentication mechanism and ACLs without touching the fronting webservers

  * A single webserver can have different URLs/applications authenticating from many 
    different authentication servers without duplicating any of their configuration or code.

  * If you use mod_auth_remote's AuthRemoteCookie support you can decrease load on the 
    authenticating servers drastically, as only 1 backend authentication per session is required.

  This is a complete rewrite of mod_auth_remote specifically for apache 2.2 (& apr 1.3). 
  I intend to add new functionality only to this version for now.

  Latest dev mod_auth_remote code is at http://github.com/saju/mod_auth_remote/tree/master

  mod_auth_remote for httpd 1.3 and 2.0 can be found at http://saju.pillai.googlepages.com/mod_auth_remote


Blog | Support | Training | Contact | API | Status | Twitter | Help | Security
© 2010 GitHub Inc. All rights reserved. | Terms of Service | Privacy Policy
Powered by the Dedicated Servers and
Cloud Computing of Rackspace Hosting®
Dedicated Server