Just so I'm on the same page here. You want to secure user access to making requests to your arcgis.war URL. Or are you trying to add security to an application that consumes the arcgis.war?
I ask because you have mentioned using tokens and also securing your web app down to the method level. The method level of your application or the method level of say an ArcGIS Geometry service?
I'm not sure what using Spring Security "and" tokens buys you. They both restrict access to the arcgis web services based on username/password.
You could deploy arcgis.war and enable security on it using ArcGIS Server Manager and get the same effect. The user consuming ArcGIS Server web service would need to authenticate, and at that point, you should be under HTTPS.
This is why I asked if you are securing the ArcGIS web service or the application that consumes your ArcGIS web service.
Your app can always generate a token in the background and supply those credentials to a secure ArcGIS web service without the user of your app even knowing. However, I get the feeling that you also want to secure the "app", which is fine - I get it, but I think your solution is trending towards unnecessary complication by fielding requests to arcgis.war via Spring Security.
Spring Security secures your app.
ArcGIS Server and possibly the web container can secure your ArcGIS Web services.
ArcGIS server manager is great but it doesn't meet our business requirements.
Hi,
Similarily to you I have an Spring application that communicates to AGS. Application is secured but services are not and they have to.
I thought about some solutions and one of them is that you described as option 1.
As I suppose there is some kind of Single Sign On at least between your application and web adaptor (services)?
Is there a possibility to get your configuration? Or even some instructions?
(unfortunatelly I can't go to link that you wrote in post)
Adam