It's not clear from your message whether you're working with Globus Connect Server v4 or v5.
Running any other software under the apache server used by Globus Connect Server version 5 is extremely unlikely to work out well, and it's not something we support. The software integrates fairly extensively with apache and expects to be able to configure new virtual hosts dynamically.
Looking at our documentation (at docs.globus.org
), I'm not certain that we make this sufficiently clear -- I'll file a change request for that, so that it's at least well-known.
Globus Connect Server v4 can make use of a separate server for its myproxy-oauth configuration. If this is what you're looking to use you (or members of your team) can reach out to us at sup...@globus.org
and we can help talk you through the configuration.
I don't believe we have a guide on this exact subject, but the steps are very similar to the general multi-node configuration which we document here:
Under v4, you can install the IO component (GridFTP) on one server and the ID (myproxy) and Web (apache + myproxy-oauth) components on another.
As for the question of yours which I left unanswered...
If we mean v4, the answer is not yet! Though it may be possible in the near future, I wouldn't recommend it even if you can.
Under both v4 and v5, Globus Connect Server's web components expect ownership of the apache configuration.
Unless you have a strong reason to do so, I would give the Globus Connect Server's apache server its own home, separate from any other applications.
To toss an idea out there, if you're dedicated to trying this configuration, you could put your app under a non-mod_wsgi server and reverse proxy with apache. uwsgi and gunicorn spring to mind as choices. That way, you eliminate any conflict between mod_wsgi for your application and mod_wsgi for Globus Connect Server.