Portal federated AGS and secured services

Question

I'm using ArcGIS Server 10.5 with secured services and trying to federate it (and hosted server) with Portal 10.5.  Whenever I do, portals security takes over and my services are no longer secured.  Should I be able to federate ArcGIS server (hosted server so users can publish in portal to it) while still keeping some services secured in AGS?

Reason I was hoping this was possible is because I've read that printing is possible as long as a custom print service (embedded login credentials) is published and the web app has secured services.

StevenE · Answer

Hi Rebecca,

I have a single machine deployment of Enterprise where Server and Portal are federated. Anonymous access is enabled in the Portal, and all feature layers, basemaps, printing/geocoding tools, and both the web map (created in Portal) and web app( created in WAB Dev, downloaded and uploaded to web server) are public as well. I added the app to Portal by connecting to the app in my content.

Yet, when opening the app, I still get prompted to login to Portal. I want to make this map available to the public and am at a loss as to the correct path to take. I've read conflicting cases of setting up a proxy being the correct action to take, or not applicable when Portal and Server are federated. Any help or information would be greatly appreciated.

Thanks,

Steven

DerekLaw · Answer

Hi Rebecca,

> ... once Portal is federated, (taking over security) items are either shared as "public" or it requires a named-user.

Yes, this statement is true. After you federate a Server site with Portal for ArcGIS, its web services will now utilize the security model configured for Portal. And yes, web services can be shared as "public" (meaning everyone on the intranet can access) or a named user account is required to access them.

Hope this helps,

RebeccaStrauch__GISP · Answer

Derek Law‌  correct me if I am wrong, but from everything I have read, and staff I have talked to, once Portal is federated, (taking over security) items are either shared as "public" or it requires a named-user.

With secure services in AGS, a proxy works well for controlling access to secure services (for web sites hosted locally). But this is not an option for Portal I don't think (from a legal licensing standpoint).  I know you can not talk licensing, but this is something users need to talk to their customer rep about, IMHO.

(I'm recommending not federating Portal in our shop, at this time, for that reason)