As in the title. We are logging in our users with the .dotnet resource Proxy hosted on our server. But when trying to print secured services the user is prompted to log in anyway.
As discussed in an older post, that's the intended behaviour.
The resource proxy will not print a secured map service. This is by design. So it is possible to use the proxy in order to authenticate and display the secured service on the map, but when it comes to printing a secured service, the resource proxy will not handle this scenario as it will not pass the token in the Web_Map_as_JSON parameter.
I spoke with the Print widget guys at the UC in San Diego a few weeks ago (June/July 2016). They told me that in order for the print service to work, the proxy must be changed so that it will add a token on to a JSON output from the client side app. Currently, as stated above, the proxy will see the request from the print widget go through, but it will not attach a token to it. It is not the easiest solution, but it is the way to go.
The possible solution above seems to be really difficult. We can't create a custom print service, since we don't want to use arg gis server.
So since some time passed since then, i wanted to ask if this is possible by now, or if someone already did these proxy modifications.