Flex Viewer 3.6 Authentication Issues

[MatthewTwietmeyer]

I inherited a few Flex Viewer applications when I took my current job that were created and configured by the old GIS professional at my company who left. Two are very basic and are easy to adjust or edit accordingly. But... I seem to have hit a snag with the last one. The web app starts with a custom configsplash screen that offers two options that go to the two config.xml file configurations admin and user. The admin configuration after clicking the object takes you to the main Flex Viewer screen and arcgiserver asks for the admin username and password. This pulls up the administration map service layer that offers the entire view of polygons in the service which works fine. The user screen takes you to a different layer that is the user operational layer map service.... this is where I can't find the configuration. There are 6 users that when prompted for their ArcGIS Server Username and Password and it is entered are only shown the polygons that they are permitted to see. I can't find where this configuration is whether its token,proxy,ssl or sql?

Any advice or help would be greatly appreciated.

Thanks,

twiet33

[RobertScheitlin__GISP]

Matthew,

     It sounds like the access to what is available to them is controlled by ArcGIS Server. Using ArcGIS Server you can assign user privileges for feature access.

[MatthewTwietmeyer]

Robert,

Thanks for replying. I see your point ...feature access is a possibility. But...the config file for the user session says that the layer is dynamic. I am now searching for something in the code for a event query or array that finds the user and field ids for that user based off their log in credentials. Just to give more detail, the 6 different users see different field polygons and field ids for there particular area. So somewhere there is a event with a dynamicmapservicelayer clause.

Thanks,

Matthew

[MatthewTwietmeyer]

Robert,

I figured it out. The config file through me off the trail thinking it was a dynamic layer and it apparently had feature access enabled originally with ownership permissions enabled with editor tracking. Thanks for the help. I'm glad I know the ins and outs of this web app now.

Matt