A forum for technical support discussion related to Fogbugz.
We've been running our own server for a while now, but will soon be working with an external contractor on the same project.
We need to give the external group access to our existing installation, which relies on the back-end LDAP authentication, but can't put the same server in the corp DMZ to make it web-visible.
Is there a way to point an on-demand site at an existing non-public (behind firewall) installation?
What options are available for this kind of setup?
I'm not sure I fully understand the situation, but I can say that On Demand sites will only be pointed at our servers and our databases, so that's probably not what you want.
You could set up a web server outside your firewall running FogBugz that would point at your FogBugz database, and poke a hole through the firewall just for that server to reach the database server. You could also IP-restrict the web server to your contractor in order to lock it down further.
Would something like that work?
I just checked and the LDAP connection is made from the webserver, which means that it probably won't work for you. Hrm. I'm not sure there's a way to set things up the way you want unless you switch to FogBugz authentication for the duration of this project or something crazy like that.
Good to know about the licensing... thanks.
as far as switching authentication modes, can that be done mid-stream? the project in question is ongoing (as in already exists, this is an add-on). If we were to eliminate LDAP, would we need to recreate user accounts for everyone, and if so, could they be matched up to the LDAP names?
The accounts will all still remain if you switch from LDAP to FogBugz authentication - FogBugz creates accounts to match LDAP and then just includes a pointer to the associated LDAP account if that's necessary.
If you turn off LDAP, you may have to manually set passwords for each of the accounts, since the passwords currently being used are coming from the LDAP server.
It would be kind of a pain, so I don't know if I recommend doing this, but I'm failing to think of other good workarounds for your situation.
I'm guessing you don't have ISA or similar available to republish the fogbugz website?
Sunday, December 9, 2007
We're not doing it now, but at my previous job, we just had FogBugz running on an internal website, and used ISA 2004 to republish the website (with https) to the outside world.
Monday, December 10, 2007
This topic is archived. No further replies will be accepted.Other recent topics