This blog post shows how to set up PKI authentication in a GeoEvent Data Store connection.
The first thing you will need to do is install certificates for both your ArcGIS Enterprise machine and your authentication provider.
The easiest way to get these certificates is to export them from your browser. On your GeoEvent machine, open a tab in your browser and enter the URL for each into the address bar. Once you’ve done this, you can access the certificate by clicking on the ‘lock’ symbol in the address bar and viewing the certificate.
Once you are viewing the certificate, go to the ‘Details’ tab and press the ‘Copy to File…’ button.
This brings up the Certificate Export Wizard
Complete this process for both your ArcGIS Enterprise and your security provider URL.
Complete this import process for both certificates. When you are done, your list of SSL Certificates should include a link for both your ArcGIS Enterprise and the security provider servers.
Finally, you will need to restart your Windows services. To do this either reboot your machine, or:
In Windows Services
On your GeoEvent machine, create a folder where you will store the PKI certificates. These certificates represent the user you will be connecting to your enterprise as. The path MUST be on the local GeoEvent machine, UNC paths are not allowed. This folder can contain one or more user certificates (.pfx files), where each certificate represents a different user.
Log in to GeoEvent Manager and go to the ‘Site | GeoEvent | Data Stores’ page. Press the ‘Register Folder’ button. On the Register Folder dialog enter the path to the folder you created above to store your certificates.
Within GeoEvent Manager, on the same Data Stores page, press the ‘Register ArcGIS Server’ button to open the ‘Register ArcGIS Server’ dialog. On the dialog, select the ‘Portal’ option at the top. Next, select the ‘Use PKI’ option to check that box.
Each connection represents a specific user. Thus, the content that is accessible by a GeoEvent Data Store connection is limited to:
Items shared with the user (e.g. through groups) will not be visible/accessible.
Because of this, it may be required to create multiple GeoEvent Data Store connections, each representing a different user. For this reason, I usually include the user’s name in the GeoEvent Data Store connection’s name. I usually suggest that organizations dedicate one “Application” user to GeoEvent and publish all content that GeoEvent will need access to under that one headless user. However, this is not always possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.