|
It looks to me as if you are at odds with yourself. Half of you wants the /admin/ folder to reside within the parent application, perhaps because it's easier to leverage available functionality and application scope parameters, etc The other half of you is paranoid, and really wants the admin folder to run as an entirely separate application, perhaps a separate J2EE deployment. That way you can apply some greater level of blanket security (like only respond to local VPN IPs or something). The solution you describe below is your way of reconciling both halves. It was just a guess. Am I close? It may be easier for us if you posted what specific type of threat you are battling with this design, whereby we could pontificate all the wonderful ways we have all dealt with such threats before. Like ssl, passwords, and well-built OnRequestStart methods. Take it from me: Beware of over-thinking your project's design to the detriment of actually releasing it in any form. I've done this myself so many times, that I actually made up the term (Application Publication Anxiety) and wrote a blog post about it to punish myself: http://akh.com/index.cfm/on-tech/it-anxieties/ Al On 8/25/2014 3:02 PM, Jason Allen
wrote:
-- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. |
Re: [OpenBD] Admin side of an app (advice)
'Alan Holden' via Open BlueDragon Mon, 25 Aug 2014 21:29:37 -0700
- [OpenBD] Admin side of an app (advice) Jason Allen
- Re: [OpenBD] Admin side of an app (... 'Alan Holden' via Open BlueDragon
- [OpenBD] Re: Admin side of an app (... Marcus F
- RE: [OpenBD] Admin side of an app (... Halo Maps
