views:

72

answers:

1

I have a web application that requires user authentication. Once logged into this web application I want the users to also be able to see the content of a read only wiki that is running on the same server but is not publicly accessible, however I do not need/want to have the users of my web application to have accounts on that wiki, and I don't want my users to have to explicitly authenticate to the wiki.

I've considered these two options:

  1. Run the wiki on localhost only, and somehow proxy requests. I think this may need some url rewriting or aliasing magic to allow users to navigate through the wiki while still going through the proxy?

  2. Write an authentication plugin for the wiki that checks the current session variables for my web application authentication, and if a user is authenticated to the web application (ie check their session variables), then grant them access.

The second is doable, but the first seems like it may be a quicker solution with the right know how. Any other ideas on how to approach this, or direction on a way to implement the first option?

I realize that the answer to this question may not be programming related, yet it also may be. I'm a programmer, and approaching this problem as such.

Edit

I've not found a solution for the reverse-proxy method. At this point, I'll be pursuing modifying the wiki itself, probably with an authentication plugin.

A: 

I think Apache as a reverse proxy may be what you want:

GrayWizardx
this looks very promising, but I can't see how it can work with authentication which occurs at the application level.
chris