 |
out of date information |
We are building web-pp up into an invitation client (in a branch). Such a client must allow you to easily invite a person you have found (picked) to use the sp on which the client it hosted. There are 3 choices for implementing this:
- Have the program modify the apache access file (XXX-vhost.xxx): This is undesirable because this file is not intended to have complex access information in it. Is is also fragile (any errors will break a lot of things).
- Write the invited users to a file of some sort and have the actual web-app check it for access: This is undesirable because we need to fiddle every tool that we try to protect this way.
- Write the invited users to a directory and have apache consult this to determine access rights: This is the approach we have chosen. Using mod_uwa, we can tell apache to check an LDAP directory after shibboleth has done its work. This keeps the invited user data neatly organised and easily accessible, removes the need for any changes to the protected tools and involves a 'normal' configuration of apache/shibboleth.