Skip to main content

Service connection not seeing secured service

Comments

1 comment

  • Permanently deleted user
    It turns out that since my GE is federated with AGOL, it cannot consume secured services from a federated Portal. It's A or B. However, here is another option offered by Latitude. If you unfederate ArcGIS Server from Portal and use token security instead, then you can create a service connection for the ArcGIS Server in Essentials Manager using a token username and password.  Token security doesn't require you to be signed into the application using any particular method- as long as you can provide the username and password to Manager, Essentials can fetch tokens on its own to provide access to the service.   I'm not sure what I would lose by unfederating the Portal since I ultimately decided to go with AGOL for most user and content management. (The reason I'm publishing services through Server at all is the labeling capacities fit my needs better.) Pros and cons...  
    0

Please sign in to leave a comment.