<?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: Is there a way to block sde clients? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444791#M25407</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you Vincent,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;didn't know about that, or maybe forgot it. The command line stuff is the only reason I have the service running.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll stop it and trust sqlnet.ora to stop our developers accidentally locking our production schema's with their&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;profiles at deployment time,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Rune&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 May 2013 03:42:31 GMT</pubDate>
    <dc:creator>runegullstrom</dc:creator>
    <dc:date>2013-05-23T03:42:31Z</dc:date>
    <item>
      <title>Is there a way to block sde clients?</title>
      <link>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444787#M25403</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I can stop oracle clients from accessing a server by blocking them using "tcp.validnode_checking = yes" in&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;my sqlnet.ora file. This will stop direct connect clients but not application server clients.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Apart from the obvious 'you should only have direct connect anyway' is there a way to block &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;specific application server clients from accessing an SDE server?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Rune&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 01:39:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444787#M25403</guid>
      <dc:creator>runegullstrom</dc:creator>
      <dc:date>2013-05-23T01:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to block sde clients?</title>
      <link>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444788#M25404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;&amp;nbsp; Apart from the obvious 'you should only have direct connect anyway' is there a way to block specific application server clients from accessing an SDE server?&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Good question.&amp;nbsp; I don't think so.&amp;nbsp; Making an application server connection is documented everywhere, so if the ArcSDE service is running on your server, there is not much you can do.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you installed SDE with the ArcSDE Service in the Post install, then the only way to block application server connections from clients making those kinds of connections is to revoke those logins until the users comply.&amp;nbsp; This is the mean option.&amp;nbsp; You gotta do what you gotta do.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Or create a SQL login for them and manage the password.&amp;nbsp; The only problem with this is if the user shares their .sde connection file with someone else.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Or reinstall ArcSDE and don't install the ArcSDE service option in the post install.&amp;nbsp; But then you lose the command line stuff.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Just be glad your users haven't figured out what else they can do with application server connections.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 02:19:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444788#M25404</guid>
      <dc:creator>LeoDonahue</dc:creator>
      <dc:date>2013-05-23T02:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to block sde clients?</title>
      <link>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444789#M25405</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You can usually configure a firewall to block application server connections&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;from all but a list of allowed IPs, but if you want to restrict certain clients&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;from all IPs, then there is no way to distinguish between client applications&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; at any time, much less at connect.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You don't lose command-line access without an application server, you just&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;need to use the Direct Connect syntax in the connection variables.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 02:27:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444789#M25405</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2013-05-23T02:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to block sde clients?</title>
      <link>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444790#M25406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Vince, totally forgot about that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://help.arcgis.com/en/geodatabase/10.0/admin_cmds/support_files/connections.htm"&gt;http://help.arcgis.com/en/geodatabase/10.0/admin_cmds/support_files/connections.htm&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 02:35:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444790#M25406</guid>
      <dc:creator>LeoDonahue</dc:creator>
      <dc:date>2013-05-23T02:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to block sde clients?</title>
      <link>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444791#M25407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you Vincent,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;didn't know about that, or maybe forgot it. The command line stuff is the only reason I have the service running.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll stop it and trust sqlnet.ora to stop our developers accidentally locking our production schema's with their&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;profiles at deployment time,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Rune&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 03:42:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/is-there-a-way-to-block-sde-clients/m-p/444791#M25407</guid>
      <dc:creator>runegullstrom</dc:creator>
      <dc:date>2013-05-23T03:42:31Z</dc:date>
    </item>
  </channel>
</rss>

