<?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: Publishing to Federated Server with SAML in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733079#M56860</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jonathan. So you are saying I should use&amp;nbsp;&lt;SPAN style="color: #4d4d4d; background-color: #fafafa;"&gt;CreateGISServerConnectionFile&lt;/SPAN&gt;&amp;nbsp;and pass into it my Federated server URL, build-in Portal account Login+Password and use such obtained .ags file to call&amp;nbsp; UploadServiceDefinition_server ?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 May 2018 13:32:16 GMT</pubDate>
    <dc:creator>SzymonPiskula1</dc:creator>
    <dc:date>2018-05-15T13:32:16Z</dc:date>
    <item>
      <title>Publishing to Federated Server with SAML</title>
      <link>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733076#M56857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I am working on an automated way of publishing map services to a Federated ArcGIS Server. The users&amp;nbsp;of the Portal come from our SAML provider. In my scripts&amp;nbsp;I want to achieve the map service publishing automation with use of arcpy. To publish an item I obviously need to connect to Portal in first place in my python script. Considering presence of SAML how&amp;nbsp; can I create a connection to Portal with arcpy so that the process could be performed as a scheduled windows batch job? What account would you recommend to use for this process? Should I create a dedicated batch-job account in SAML or actually try to publish via some Porta build-in account, but then would that be possible having SAML? What pattern for this process would you recommend?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Szymon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 15:31:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733076#M56857</guid>
      <dc:creator>SzymonPiskula1</dc:creator>
      <dc:date>2018-04-26T15:31:09Z</dc:date>
    </item>
    <item>
      <title>Re: Publishing to Federated Server with SAML</title>
      <link>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733077#M56858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Szymon,&lt;/P&gt;&lt;P&gt;Use a geodatabase user with create privileges to create the feature class.&lt;/P&gt;&lt;P&gt;Then run the python script as a windows scheduled task using a domain account such as the one running ArcGIS Server's and Portal for ArcGIS windows services.&lt;/P&gt;&lt;P&gt;You can knock out a quick model builder of it, export as python script and then setup the windows task.&lt;/P&gt;&lt;P&gt;-Bill&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 16:05:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733077#M56858</guid>
      <dc:creator>BillFox</dc:creator>
      <dc:date>2018-04-26T16:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: Publishing to Federated Server with SAML</title>
      <link>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733078#M56859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you still have the built-in IAA account or any other administrative account that isn't SAML? If so, just create your GIS Server connection file using that account and then use it to publish the services.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 17:04:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733078#M56859</guid>
      <dc:creator>JonathanQuinn</dc:creator>
      <dc:date>2018-04-26T17:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: Publishing to Federated Server with SAML</title>
      <link>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733079#M56860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jonathan. So you are saying I should use&amp;nbsp;&lt;SPAN style="color: #4d4d4d; background-color: #fafafa;"&gt;CreateGISServerConnectionFile&lt;/SPAN&gt;&amp;nbsp;and pass into it my Federated server URL, build-in Portal account Login+Password and use such obtained .ags file to call&amp;nbsp; UploadServiceDefinition_server ?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2018 13:32:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733079#M56860</guid>
      <dc:creator>SzymonPiskula1</dc:creator>
      <dc:date>2018-05-15T13:32:16Z</dc:date>
    </item>
    <item>
      <title>Re: Publishing to Federated Server with SAML</title>
      <link>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733080#M56861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that's right. I think SAML will be difficult to manage in arcpy as that involves an external identity provider.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2018 23:31:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/publishing-to-federated-server-with-saml/m-p/733080#M56861</guid>
      <dc:creator>JonathanQuinn</dc:creator>
      <dc:date>2018-05-15T23:31:51Z</dc:date>
    </item>
  </channel>
</rss>

