Thanks to you both for replying so quickly. I'm quite interested in seeing the 'single bd instance' install (especially if it can work with Jetty--I'm not sure I'm ready for Tomcat/Apache yet :). But to get to the immediate question, let me try to clarify.
Ideally, I'd like to remove the OpenBD admin interface from public access altogether (similar to the way the CF Admin isn't necessarily connected to the virtual host). But short of that, I'd like to be able to use the OBD Admin option that allows me to restrict admin access by ip address. To restate the situation, I have two virtual hosts running under the same Jetty instance in two side-by-side subdirectories under webapps. Each one has its own set of OBD files from the WAR. In the Jetty contexts, one is set to respond on the ip address of the server, and the other is set to a named subdomain. At this point (not having made any changes to the OBD admin settings) everything is working fine-- both sites properly respond to external browser requests (one by ip address and one by domain name), and serve up cfm templates brilliantly (you guys are awesome, btw, for making this possible :). The trouble comes when I configure the OBD admin to restrict access by IP. In the ip-address-configured instance (which responds to my server's public ip address as well as my internal 192.168 addresses), I can put my internal network wildcard (192.168.1.*) into the allow access field in the Admin screen, and all is well--only requests from my internal network are able to access the OBD admin pages. However, in the other virtual host, that is set in Jetty to respond only to a named subdomain (http://lunchboxes.muradaz.com), if I put the internal network wildcard into that admin, I'm immediately locked out of the admin for that virtual host, and have to go into the xml file to reset the allowedip by hand to be able to restore access. To be clear, I'm only using the ip address wildcard, not entering the subdomain name in the admin screen. This problem persists even if I add the public ip address of the server. I threw in a cgi.remote_addr tag to the display page, to confirm that my named subdomain site is properly reporting the requesting ip address as part of my internal network, but I'm still not able to access the admin pages. I hope this clarifies the problem. Apologies for being so verbose, but I'm trying to get my brain around all of this (very new for me) stuff, and I find that writing it all out helps me organize it in my brain. Thanks again for all your input--I look forward to hearing from you soon. I'd also be happy to volunteer as a guinea pig for any 'Dummies Guide' how-to on installation and configuration--I have a lot of Windows experience, but the GUIs have dulled my 'manual configuration' skills, so I'm a great candidate to play the 'if he can get it, anyone can' role :). Cheers, REM O- > Just want to make sure I'm understanding. So you set the IP address > range, and that works. But when you use the hostname in your browser, > even if that hostname resolves to an IP address in the range you've > specified, it doesn't work. > > My first point of confusion is that you have to reset the values in > bluedragon.xml. You aren't putting the hostname in the admin as opposed > to an IP address are you? > > I'm happy to help troubleshoot to see if there's something up with the > admin console code. > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
