Hi, I have a pmapper instance and would like to use drupal auth system in order to access several maps (pmapper configs).
Target is to serve different pmapper configs according to users profile attributes: eg. if user A has xy attribute I serve config=xy, etc etc So I placed an include in index.phtml which loads drupal user data, parses the attributes, check if is logged and then redirects him to map_default.phtml?config=CONFIG Problem arise because the user can change the url and switch to other config which doesn't belog to him after the maps is loaded. How can I prevent this? is there any clever way to do this routing according to "who the user is"? /regards -- « Nunc est bibendum, nunc pede libero pulsanda tellus » ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
