The addAttachment operation fails on an ArcGIS Server 10.4.1 secured feature service's related table when the service is accessed via utility.arcgis.com after it is registered as an item in ArcGIS Online with the credentials embedded in the item.
上次发布: July 28, 2017ArcGIS Online
漏洞 ID 编号
BUG-000098577
已提交
August 12, 2016
上次修改时间
June 25, 2025
适用范围
ArcGIS Online
找到的版本
N/A
操作系统
Windows OS
操作系统版本
N/A
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
解决办法
Use the direct ArcGIS Server URL to add attachments to this feature service's related table.
Customer's use-case for the need to add attachments through "utility.arcgis.com":
1. They have a custom desktop application built using WPF and ArcGIS Runtime SDK for .NET.
2. The application requires an ArcGIS Online login to authenticate the user using the OAuth pattern to obtain an authorization token.
3. The application downloads a custom configuration file that contains information telling the client what feature layers it will be working with.
4. The feature service is referenced in the config file using it's ArcGIS Online content item ID.
5. The client then obtains the URL to the feature service from that ID. Note that the URL contains "utility.arcgis.com".
6. This pattern of accessing the ArcGIS Server service via ArcGIS Online is necessary to the application so as to allow the user to only require one login, their ArcGIS Online organization login.
7. It allows the curator of the services and application configurations to share a medley service references that may come from a variety of sources and security domains to the end user through the application without having to explicitly give the user multiple sets of credentials to access all the different services, simply by using the content sharing patterns offered by ArcGIS Online.
8. Otherwise, the end user would not only have to login to ArcGIS Online, they would have to login to each ArcGIS Server service they are connecting to manually, which would not present a user friendly application experience.