Re: Shibboleth authentication for Roundup
Georg Lehner <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Organization | MagmaSoft |
| Message-ID | <[email protected]> |
On 02/23/2017 10:37 AM, Tonu Mikk wrote: [..] > > <VirtualHost xxx.xxx.xxx.xxx:443> > ServerName mydomain.com <http://mydomain.com> > ServerAdmin [email protected] <mailto:[email protected]> > > AliasMatch ^/@@file(.*) /swadm/roundup/trackers/wcag/html$1 > AliasMatch ^/(?!@@file)(.*) > /swadm/roundup/trackers/wcag/html/dummy.py/$1 <http://dummy.py/$1> > > DocumentRoot /swadm/roundup/trackers/wcag/html > > <Directory /swadm/roundup/trackers/wcag/html> > # Default allow policy > Order Deny,Allow > AuthType shibboleth > ShibRequestSetting requireSession 1 > Require valid-user > RequestHeader set REMOTE-USER %{REMOTE_USER}s > > </Directory> > > AddHandler python-program .py > PythonOptimize On > PythonPath "sys.path + ['/usr/lib64/python2.6/site-packages']" > PythonHandler roundup.cgi.apache > PythonOption TrackerHome /swadm/roundup/trackers/wcag > PythonDebug On > > # SSL information omitted for brevity. > </VirtualHost> > > Python Debug: > > MOD_PYTHON ERROR > > ProcessId: 23377 > Interpreter: 'mydomain.com <http://mydomain.com>' > > ServerName: 'mydomain.com <http://mydomain.com>' > DocumentRoot: '/swadm/roundup/trackers/wcag/html' > > URI: '/Shibboleth.sso/SAML2/POST' > Location: None > Directory: None > Filename: '/swadm/roundup/trackers/wcag/html/dummy.py' > PathInfo: '/Shibboleth.sso/SAML2/POST' > > Phase: 'PythonHandler' > Handler: 'roundup.cgi.apache' > [..] Hello, The first AliasMatch lines, would not match '/Shibboleth.sso...' The second seems to be a contrived way of "match anything else", and maps '/Shibboleth.sso/...' to: /swadm/roundup/trackers/wcag/html/dummy.py/Shibboleth.sso/SAML2/POST' which is not what you want. You could rather do something like: AliasMatch ^/(?!Shibboleth.sso)(.*) /swadm/roundup/trackers/wcag/html/dummy.py/$1 so that '/Shibboleth.sso...' is not matched and handled otherwise by Apache. IMHO a more stable approach would be a good planning of URI namespaces, where your tracker uris are prefixed by some path, e.g. '/issues'. This eases the matching magic. The "landing page" '/' could simply redirect to '/issues/something' if you can't or don't want to communicate the '/issues' prefix to your users. Best Regards, Georg Lehner ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot