AnsweredAssumed Answered

Secure layer options

Question asked by JRonde on Aug 19, 2016
Latest reply on Aug 31, 2016 by JRonde

I've created a map with the ArcGIS API for JavaScript similair to the one in the samples (Legend | ArcGIS API for JavaScript 3.17). I've split all layer options in a seperate layerConfig.js file so that I can easily add/remove layers withouth changing the rest of the application. The layers in this config file are served by an ArcGIS server and are secured with token based authentication and user login. That works fine. The application asks for a login before you can actually see any data on the map. The problem is that the layerConfig file contains urls and layernames that might be sensitive to our clients and I don't want them to be public accessible. 


What's the best practice to secure this kind of config information?