This proxy is a J2EE Web Application that can be used in conjunction with ArcGIS GeoEvent Extension for Server or GeoEvent Processor for Server to ease the manageability of ArcGIS Data Store connections. This is intended for use with GeoEvent Extension 10.3.0 or GeoEvent Processor 10.2.2 and earlier.
- Create proxied connections to ArcGIS Server or Portal where the proxy Web Application manages the tokens for the user.
- Place copies of the self-signed certificates inside of a directory so that the proxy automatically trusts those certificates. With this feature you won't have to touch the JRE's cacerts file to get connections to work.
- Configure username and passwords for both the Web Tier and GIS Tier
To Build:
Building the source code:
- Make sure Maven is installed on your machine.
- Run 'mvn package'
Deploying built WAR file:
- Using an instance of Tomcat, copy the generated file target/geoevent-datastore-proxy.war to TOMCAT_HOME\webapps
- Run your instance of Tomcat.
###Servers
Once the webapplication has been unzipped, you will find a file TOMCAT_HOME\webapps\geoevent-datastore-proxy\WEB-INF\classes\arcgisservers.properties This file holds the configurations for all of the proxied connections you want to make.
Below is a sample configuration
servers=javidel,portalhostqa,portaliwaqa
javidel.url=http://javidel:6080/
javidel.tokenUrl=https://javidel:6443/arcgis/tokens/generateToken
javidel.gisTierUsername=publisher
javidel.gisTierPassword=publisher
javidel.username=
javidel.password=
portalhostqa.url=https://portalhostqa/
portalhostqa.tokenUrl=https://portalhostqa/gis/sharing/rest/generateToken
portalhostqa.gisTierUsername=username
portalhostqa.gisTierPassword=password
portalhostqa.username=
portalhostqa.password=
portaliwaqa.url=https://portaliwaqa/
portaliwaqa.tokenUrl=https://portaliwaqa/gis/sharing/rest/generateToken
portaliwaqa.gisTierUsername=
portaliwaqa.gisTierPassword=
portaliwaqa.username=
portaliwaqa.password=
This configuration configure the proxy for 3 servers.
- javidel: ArcGIS Server that uses tokens to secure servers.
- portlhostqa: A portal instance that uses tokens to secure services
- portaliwaqa: A portal instance that uses IWA to protect its services.
The main entry for the configuration is the servers property. This property is a Comma Separated Values (CSV) list of server names that you want to configure. Each element in the CSV list will server as a key to other properties within the properties file. For each serverName, you can configure the following properties:
- <serverName>.url REQUIRED
The base URL that you want to proxy. Usually http://myhost.com/
- <serverName>.tokenUrl
The URL where the proxy should POST a request to generate a token. This must end with `generateToken`
otherwise the POST operation will most likely fail and the proxy will not send any tokens with requests.
If not present, then the proxy will not append or replace any tokens associated with proxied requests.
- <serverName>.username
The username to present to the server when WebTier authentication is requested.
- <serverName>.password
The password to present to the server when WebTier authentication is requested.
- <serverName>.gisTierUsername
The username to pass to the generateToken request.
- <serverName>.gisTierPassword
The password to pass to the generateToken request.
####Configuration Use Cases
The configuration for javidel is for an ArcGIS Server that uses tokens to protect some of its services. It is a stand-alone ArcGIS Server. You would visit http://javidel:6080/arcgis/rest/info?f=pjson to retrieve the server's information and see the following:
{
"currentVersion": 10.3,
"fullVersion": "10.3.0",
"soapUrl": "http://javidel:6080/arcgis/services",
"secureSoapUrl": "https://javidel:6443/arcgis/services",
"authInfo": {
"isTokenBasedSecurity": true,
"tokenServicesUrl": "https://javidel:6443/arcgis/tokens/",
"shortLivedTokenValidity": 1
}
}
From the JSON, we see that the token url is at https://javidel:6443/arcgis/tokens/, but we need the endpoint where we want to POST the token request, so we add generateToken to the path. So the property javidel.tokenURL=https://javidel:6443/arcgis/tokens/generateToken gets set.
Since the javidel server does not use WebTier authentication, we leave the javidel.username and javidel.password entries blank. Since the tokens are needed for GISTier authentication, we supply the javidel.gisTierUsername and javidel.gisTierPassword properties.
#####portalhostqa (Portal with GIS Tier authentication using tokens) The configuration for portalhostqa is for an ArcGIS Portal Server that uses tokens to protect its services. You visit https://portalhostqa/gis/sharing/rest/info?f=pjson to retrieve the server's information and see the following:
{
"owningSystemUrl": "https://portalhostqa/gis",
"authInfo": {
"tokenServicesUrl": "https://portalhostqa/gis/sharing/rest/generateToken",
"isTokenBasedSecurity": true
}
}
From the JSON, we see that the token url is at https://portalhostqa/gis/sharing/rest/generateToken. So the property portalhostqa.tokenUrl=https://portalhostqa/gis/sharing/rest/generateToken gets set.
Since the portalhostqa server does not use WebTier authentication, we leave the portalhostqa.username and portalhostqa.password entries blank. Since the tokens are needed for GISTier authentication, we supply the portalhostqal.gisTierUsername and portalhostqa.gisTierPassword properties.
The configuration for portaliwaqa is for an ArcGIS Portal Server that uses Integrated Windows Authentication (IWA) to protect its services. You visit https://portaliwaqa/gis/sharing/rest/info?f=pjson to retrieve the server's information and see the following:
{
"owningSystemUrl": "https://portaliwaqa/gis",
"authInfo": {
"tokenServicesUrl": "https://portaliwaqa/gis/sharing/rest/generateToken",
"isTokenBasedSecurity": true
}
}
From the JSON, we see that the token url is at https://portaliwaqa/gis/sharing/rest/generateToken. So the property portaliwaqa.tokenUrl=https://portaliwaqa/gis/sharing/rest/generateToken gets set.
For this configuration to work, the Tomcat process must be run as a user that has the appropriate access privileges to consume the services since we did not provide neither username nor password for the WebTier nor the GIS Tier. The proxy will impersonate the user that is running the Web Application process when communicating with the server in this case. If the user that is running the process cannot consume the services, then this configuration would need the portaliwaqa.username and portaliwaqa.password properties set to consume the services. IWA enabled Portals return a token as soon as you visit the generateToken endpoint, so there is no need to supply values for the properties portaliwaqa.gisTierUsername andportaliwaqa.gisTierPassword. When configuring the username with a DOMAIN/username format, use the forward slash / or an escaped backslash \\ otherwise the username will not be interpreted correctly. So the following 2 entries would be valid portaliwaqa.username=DOMAIN/user or portaliwaqa.username=DOMAIN\\user.
####Certificates If any of the sites you're connecting to use self-signed Https certificates, then you can export them using the browser and place them in the directory <TOMCAT>/webapps/geoevent-datastore-proxy/WEB-INF/classes/certificates with the ending of .crt, .cer, or .pem. Any certificate listed in the directory will be trusted by the proxy when making https connections.
###When to restart the proxy A restart of the geoevent-datastore-proxy web application will be required after making modifications to either the arcgisservers.properties file or dropping a new certificate file into the certificates directory. It is recommended you restart the Tomcat server in these cases although you may be able to simply restart the geoevent-datastore-proxy web application by using Tomcat's Manager application.
###Configuring GeoEvent DataStores Once you've got the proxy configured, you can point GeoEvent DataStores to use the proxy's endpoints instead of going directly to the ArcGIS Server or Portal. The screen shots for the rest of this section assume the Tomcat proxy is running at http://localhost:8080/geoevent-datastore-proxy/ (where localhost would be the same machine where GeoEvent is running).
####javidel Here are the configurations for javidel:
####portalhostqa Here are the configurations for portalhostqa:
NOTE: when configuring with GeoEvent 10.2.2 and earlier, you'll need to enter some value for the token when configuring a Portal connection. You can enter any string here when using the proxy since the proxy will replace the token before sending the request to the ArcGIS Server or Portal
####portaliwaqa Here are the configurations for portaliwaqa:
NOTE: when configuring with GeoEvent 10.2.2 and earlier, you'll need to enter some value for the token when configuring a Portal connection. You can enter any string here when using the proxy since the proxy will replace the token before sending the request to the ArcGIS Server or Portal
Find a bug or want to request a new feature? Please let us know by submitting an issue.
Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.
Copyright 2015 Esri
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
A copy of the license is available in the repository's license.txt file.