<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Securing WMS or WFS layers with something other than token in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/securing-wms-or-wfs-layers-with-something-other/m-p/1134833#M32251</link>
    <description>&lt;P&gt;The way that I've always treated this discussion with my clients is that IWA (Windows) or PKI/LDAP (Linux) is an authentication step before you get to the Enterprise Portal, i.e. the Web Adaptor determines if you can pass through to the Portal Component.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Simply,&amp;nbsp; if you're registered not in the AD/LDAP, you're not getting to the Enterprise Portal.&lt;/P&gt;&lt;P&gt;This means this approach excludes the use of Portal Tokens and SAML2.&amp;nbsp; For those options to work, you have to be able to pass through the Web Adaptor anonymously.&lt;/P&gt;&lt;P&gt;Therefore, I do not believe you can do both authentication options from the same portal.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the OGC/Security front, if you have a non-federated ArcGIS Server, then you can get creative with the authentication in front of it.&amp;nbsp; IP to IP restrictions, HTTP Basic etc - however, this is going to be global security to the server, and is not web-service specific.&amp;nbsp; That can be limiting.&amp;nbsp; The wider issue that I've observed is that there is no true security/authentication standard for OGC clients, and with so many options out there, I'd argue that some of those developers need to incorporate esri tokens security as an option/addin/extension to their products.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's an interesting/grey area that has tripped several of my clients up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jan 2022 23:31:22 GMT</pubDate>
    <dc:creator>Scott_Tansley</dc:creator>
    <dc:date>2022-01-18T23:31:22Z</dc:date>
    <item>
      <title>Securing WMS or WFS layers with something other than token</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/securing-wms-or-wfs-layers-with-something-other/m-p/1134756#M32250</link>
      <description>&lt;P&gt;We are looking for ways to share some of our hosted feature layers with another non-Esri GIS system. We know they can ingest WMS/WFS OGC services and that we can secure these services and authenticate using tokens.&lt;/P&gt;&lt;P&gt;But we would like to look into a more secure option for these services; is there anyway other than enabling LDAP and PKI (&lt;A href="https://enterprise.arcgis.com/en/portal/10.7/administer/linux/use-ldap-and-pki-to-secure-access-to-your-portal.htm" target="_blank"&gt;https://enterprise.arcgis.com/en/portal/10.7/administer/linux/use-ldap-and-pki-to-secure-access-to-your-portal.htm&lt;/A&gt;) to secure services with certs or keys?&lt;/P&gt;&lt;P&gt;Would it be possible to keep using built-in Portal accounts as the primary form of authentication and enable LDAP/PKI for a few use cases? Has anyone else tried anything like this before?&lt;/P&gt;&lt;P&gt;We are running ArcGIS Enterprise 10.7.1 on Linux.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 19:55:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/securing-wms-or-wfs-layers-with-something-other/m-p/1134756#M32250</guid>
      <dc:creator>AbigailStephens</dc:creator>
      <dc:date>2022-01-18T19:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Securing WMS or WFS layers with something other than token</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/securing-wms-or-wfs-layers-with-something-other/m-p/1134833#M32251</link>
      <description>&lt;P&gt;The way that I've always treated this discussion with my clients is that IWA (Windows) or PKI/LDAP (Linux) is an authentication step before you get to the Enterprise Portal, i.e. the Web Adaptor determines if you can pass through to the Portal Component.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Simply,&amp;nbsp; if you're registered not in the AD/LDAP, you're not getting to the Enterprise Portal.&lt;/P&gt;&lt;P&gt;This means this approach excludes the use of Portal Tokens and SAML2.&amp;nbsp; For those options to work, you have to be able to pass through the Web Adaptor anonymously.&lt;/P&gt;&lt;P&gt;Therefore, I do not believe you can do both authentication options from the same portal.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the OGC/Security front, if you have a non-federated ArcGIS Server, then you can get creative with the authentication in front of it.&amp;nbsp; IP to IP restrictions, HTTP Basic etc - however, this is going to be global security to the server, and is not web-service specific.&amp;nbsp; That can be limiting.&amp;nbsp; The wider issue that I've observed is that there is no true security/authentication standard for OGC clients, and with so many options out there, I'd argue that some of those developers need to incorporate esri tokens security as an option/addin/extension to their products.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's an interesting/grey area that has tripped several of my clients up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 23:31:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/securing-wms-or-wfs-layers-with-something-other/m-p/1134833#M32251</guid>
      <dc:creator>Scott_Tansley</dc:creator>
      <dc:date>2022-01-18T23:31:22Z</dc:date>
    </item>
  </channel>
</rss>

