Last episode we got as far as creating a map service to view a few of the nearby places Doctor Who has been seen but it is now time to find out what galactic federation has taken control of our . security
Knowing my server box was a lot bigger on the inside, I decided when Portal for ArcGIS is installed to give its Web Adaptor the name ‘portal’ as I wanted to leave the more familiar ‘arcgis’ application name for the ArcGIS Server which was also installed.
So for Portal for ArcGIS to federate ArcGIS for Server you log into the Portal as an administrator and with My Organisation choose Edit Settings and Servers.
However before federating you may see that you may need to travel back in time and do some security configuration with the ArcGIS Server.
The ArcGIS Server needs to be able to support HTTPS as we want to hide user names and passwords when we authenticate.
An ArcGIS Server can also be configured to be a Hosted Server.
Security has changed
So now we can ‘change the locks’ for any new ArcGIS Server we can temporarily administer, and unless the server administrator can still use the Primary Site Administrator login they have to come to our portal for a key (token). Galactic domination is within reach.
Returning to the search for Doctor Who
As we were federated with portal when we published a service an item was added to the portal which can be searched for.
ArcGIS Desktop will use ArcGIS Online as the default portal to sign in to, otherwise another portal can be configured via ArcGIS Administrator and then signed in to.
Now you can search another portal from ArcGIS Desktop also in a couple of ways.
Or configure and use it from another client of Portal for ArcGIS.
Activating the chameleon circuit of the Web Adaptor (not recommended by Esri)
Not only can you have many Web Adaptors for an ArcGIS Server site, a single Web Adaptor can refer to both Portal for ArcGIS and ArcGIS for Server, so we could have used the default arcgis name when first setting up Portal for ArcGIS, at the risk of some initial confusion.
So now this Web Adaptor knows how to send requests on to both the ArcGIS Server and Portal.
Again the only trick is that the portal connection in Catalog has the fully qualified name. The dark side of this trick is that it may block some future actions like federation. A better future may be to install two web adaptors eg ‘arcgis’ for the Portal and ‘arcgisserver’ for ArcGIS Server.