| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| nginx-sso-1.0.15-3.el6.x86_64.rpm | 2013-04-02 | 545.6 kB | |
| nginx-sso-1.0.15-3.el6.src.rpm | 2013-04-02 | 730.0 kB | |
| nginx_mod_sso-0.2.3.tar.gz | 2013-04-02 | 6.0 kB | |
| mod_sso-0.3.1-1.el6.x86_64.rpm | 2013-04-02 | 25.0 kB | |
| mod_sso-0.3.1-1.el6.src.rpm | 2013-04-02 | 92.1 kB | |
| apache_mod_sso-0.3.1.tar.gz | 2013-04-02 | 88.8 kB | |
| nginx_mod_sso-0.2.2.tar.gz | 2010-12-02 | 6.7 kB | |
| nginx_mod_sso-0.2.1.tar.gz | 2010-12-01 | 6.4 kB | |
| README.txt | 2010-11-30 | 3.2 kB | |
| nginx_mod_sso-0.2.tar.gz | 2010-11-30 | 7.0 kB | |
| apache_mod_sso-0.2.tar.gz | 2010-11-30 | 317.2 kB | |
| nginx_mod_sso-0.1.2.tar.gz | 2010-11-25 | 5.7 kB | |
| apache_mod_sso-0.1.1.tar.gz | 2010-11-24 | 676.0 kB | |
| Totals: 13 Items | 2.5 MB | 0 |
#########################################################################
#
# Apache Installation
#
#########################################################################
autoconf
automake -a
./configure --with-apache-includes=/usr/include/httpd \
--with-curl-config=/usr/bin/curl-config \
--with-apr-config=/usr/bin/apr-1-config
make
cp -a .libs/libmodsso.so* /your/apache/modules/directory
Config
------
See below a sample configuration file.
##################################################
LoadModule mod_sso_module modules/mod_sso.so
NameVirtualHost *:80
<VirtualHost *:80>
ServerName sso.sergrhtest.net
DocumentRoot /some/directory/with/the/sso/files/
</VirtualHost>
<VirtualHost *:80>
ServerName www.sergrhtest.net
DocumentRoot /location/of/your/web/
<Location /private>
SSOCookieName "sso"
SSOLoginUrl "http://sso.sergrhtest.net/index.php?redirect_to={URL}"
SSOLogoutUrl "http://sso.sergrhtest.net/logout.php?redirect_to={URL}"
#SSOAccessCheckerUrl "http://sso.sergrhtest.net/access.php?url={URL}&client_ip={CLIENT_IP}"
SSOAccessCheckerUrl "http://sso.sergrhtest.net/access.php?url={URL}"
</Location>
</VirtualHost>
#################################################
Change the URL according to your environment. You can set up the variables with
this effect:
- LoginUrl:
The {URL} variable will contain the web page you tried to visit and
you've been denied access. You can use it redirect the user after a
successful login
- LogoutUrl:
Same as with Login
- AccessCheckUrl:
Two possible options here. If you want to check if the user has access
to certain {URL}, set it up. You can also check if the user's IP is
allowed - {CLIENT_IP}. If you just want to check whether the user is
logged in, omit the variables.
#########################################################################
#
# NGiNX
#
#########################################################################
Configuration
-------------
Add to you nginx.conf
location /protected {
sso_cookie "sso";
sso_login_url "https://sso.server.net:443/login.php?redirect_to={URL}";
sso_logout_url "https://sso.server.net:443/logout.php?redirect_to={URL}";
sso_access_url "http://sso.server.net:80/access.php?url={URL}&client_ip={CLIENT_IP}";
root html;
index index.html;
}
If you can, don't expose the access.php to the outside world. Set it up on an
internal server or at least use the "allow" / "deny" options so that just
your sso nginx server can connect to it.
Change the URL according to your environment. You can set up the variables with
this effect:
- LoginUrl:
The {URL} variable will contain the web page you tried to visit and
you've been denied access. You can use it redirect the user after a
successful login
- LogoutUrl:
Same as with Login
- AccessCheckUrl:
Two possible options here. If you want to check if the user has access
to certain {URL}, set it up. You can also check if the user's IP is
allowed - {CLIENT_IP}. If you just want to check whether the user is
logged in, omit the variables.