It appears you’re facing a common hurdle when trying to implement Print Proxies in an older ArcGIS environment. Specifically, you’re using Web App Builder (WAB) version 1.3 with ArcGIS Server 10.2.2 and aiming to print secured imagery without prompting users for credentials. Let’s break down the issues and explore potential solutions.
You’ve correctly identified the need to embed credentials to bypass login prompts for your users. Creating a custom print service with embedded credentials is a standard approach, and setting it to synchronous is also appropriate for web applications. However, the problem arises when integrating this with WAB 1.3 and ArcGIS Server 10.2.2.
Despite pointing your WAB 1.3 application to the custom print service with embedded credentials, you’re still encountering username/password requests. This indicates a limitation in how WAB 1.3 and ArcGIS Server 10.2.2 handle print proxies and credential passthrough, particularly with secured services accessed through the Basemaps widget.
You’ve also experimented with setting up a proxy for the secured aerial imagery service, which is essential for loading it within the Basemaps widget, and this part is functioning correctly. However, the proxy setup alone isn’t resolving the credential prompt during printing.
Embedding a token directly into the print service URL proved successful for printing non-secured vector layers from “Server 2” (layers in the LayerList). This confirms that the basic print service functionality is working. The core issue lies with the secured imagery layer hosted on “Machine 1” and accessed via the Basemaps widget.
Attempting to use the print service with an unlocked security setting resulted in a timeout, suggesting that the proxy, even if configured, isn’t effectively handling the secured service in this specific scenario. The ‘undefined’ error in the console and network traffic further points to a communication breakdown when WAB 1.3 tries to access the secured imagery through the print service.
The Core Question: Is an Upgrade Necessary?
Based on your troubleshooting and the limitations of older ArcGIS versions, upgrading to ArcGIS Server 10.3+ is indeed the most recommended and straightforward solution. ArcGIS Server 10.3 and later versions have significant enhancements in handling secured services, proxies, and print workflows within Web App Builder and ArcGIS Online environments. These newer versions are designed to more seamlessly manage credential passthrough and token-based authentication, which are crucial for embedding credentials for print proxies.
Potential Workarounds (With Limitations):
While upgrading is the ideal path, let’s consider potential workarounds, although their feasibility and success are not guaranteed with WAB 1.3 and ArcGIS Server 10.2.2:
-
Token Service: Instead of embedding credentials directly in the print service URL, explore using an ArcGIS Server token service. Your WAB 1.3 application could programmatically obtain a token from the token service and append it to the print service URL dynamically before initiating the print task. This approach adds complexity to the WAB application’s code and might still face compatibility issues with WAB 1.3’s print widget.
-
Proxy Configuration Review: Double-check your proxy configuration for ArcGIS Server. Ensure the proxy is correctly configured to forward credentials or tokens for the secured imagery service. However, given the age of ArcGIS Server 10.2.2, the proxy capabilities might be limited compared to newer versions.
-
Basemap Alternatives: If feasible, consider using a different basemap source that does not require authentication for printing. This might involve using publicly available basemaps or re-hosting the imagery in a non-secured manner (if licensing and security policies allow). This is less than ideal if the secured imagery is a critical requirement.
Conclusion:
In summary, while you’ve explored several valid approaches to embed credentials for print proxies, the limitations of Web App Builder 1.3 and ArcGIS Server 10.2.2 appear to be the primary obstacle. Upgrading to a more recent version of ArcGIS Server (10.3+) is strongly advised to fully leverage print proxy capabilities and ensure seamless printing of secured services within Web App Builder. Workarounds might exist, but they are likely to be complex, potentially unreliable, and may not fully resolve the underlying compatibility issues. For a robust and supported solution, upgrading your ArcGIS infrastructure is the most effective path forward.
