Latest Contributions by LanceCole

Did you try the Dissolve Tool? ... View more

@DominicRobergeIADOT, Oh the fun of coordinate systems and transformations. WGS 1984 Web Mercator (auxiliary sphere) would be a good choice for a multi state area that you described.  That being said, you must be cognitive of what coordinate system your existing data and imagery are projected and even more importantly what transformations are being applied. When you see a discrepancy, as you have noted, typically you are working with different coordinate systems between your map and the data.  Most commonly an incorrect or no transformation has been applied.  Transformations are selected in the next section of the map properties of ArcGIS Pro.   Please also make sure you have downloaded and installed the ArcGIS Coordinate System Data from my.esri.com appropriate for your ArcGIS version. ... View more

@LukasStadelmann, Yes, you can edit existing widgets.  This does require the use of Developer Edition of ArcGIS Experience Builder and you need to host these widgets.  The original files for the table widget can be found in the ArcGISExperianceBuilder installation folder: ..\ArcGISExperienceBuilder\client\dist\widgets\common\table\src. It is best to load the entire ..\ArcGISExperienceBuilder\client folder into your code editor, such as VSCode. Below are several links for videos on customizing widgets.  They do focus on starting from a sample widget but provide some insight into how the widgets are assembled. ArcGIS Experience Builder: Customizing and Extending  Developing with ArcGIS Experience Builder  ArcGIS Experience Builder: Building Web Solutions, Advanced Topics  Customize Widgets in ArcGIS Experience Builder with ReactJS & ArcGIS API for JS (part 1)   Customize Widgets in ArcGIS Experience Builder with ReactJS & ArcGIS API for JS (part 2)  Customize Widgets in ArcGIS Experience Builder with ReactJS & ArcGIS API for JS (part 3)  How to deploy Customized Widgets of ArcGIS Experience Builder on ArcGIS Portal  ... View more

Yes, Still showing on our accounts.  As @Scott_Tansley noted, reach out to customer support or your account manager. ... View more

@Jen_Zumbado-Hannibal,  We are trying to do the opposite and access our portal data via AGOL. One of the main reasons is our imagery is in the terabyte range and would be prohibitive to host on AGOL.  The second is we need near real-time data updates for our spatial data.  We did attempt to utilize a distributed collaboration by reference but still ran into the issue of not being able to store user credentials while utilizing web-tier authentication. We did find a resolution by utilizing SAML authentication on our portal while still being able to access the data via a built-in user account. ... View more

Thanks to a comment by @BillFox posted on the idea referenced above, we were able to get SSO working with SAML on our internal network while still allowing AGOL to access using ArcGIS built-in account.  We are using Windows ADFS as our SAML Identity Provider.  It turns out that not all browsers are initially configured as WIA Supported User Agents by ADFS.  By running the following command in PowerShell we added the missing browsers utilized by our users.   Set-ADFSProperties -WIASupportedUserAgents @("MSAuthHost/1.0/In-Domain", "MSIE 6.0", "MSIE 7.0", "MSIE 8.0", "MSIE 9.0", "MSIE 10.0", "Trident/7.0", "MSIPC", "Windows Rights Management Client", "Firefox/25.0", "Firefox/47.0", "Mozilla/4.0", "Mozilla/5.0", "Chrome", "Edg/", "Edge/")   Configure browsers to use Windows Integrated Authentication (WIA) with AD FS  Note that Firefox also requires some client-side configuration. Type in about:config and add the address of your ADFS server (e.g. fs.domain.com) to network.automatic-ntlm-auth.trusted-uris.  This can be completed via GPO. ... View more

Yes, IWA or SAML and built-in users work fine when configured for portal-tier authentication.  However,  SSO does not work in this configuration and authenticated users are prompted to login to access secure services.  This is by design and documented in the links above.  When using portal-tier authentication one can access secure services using stored credentials on AGOL and make them public using a built-in account. If the enterprise deployment is changed to web-tier authentication, the SSO works great but you can no longer store credentials on AGOL to access the secure services from the portal.  You are not even offered the option to toggle this function.  It is my understanding that AGOL can only work with token based authentication and does not support web based authentication which is required. There is a question posted at Allow AGOL access to a secured enterprise portal if you have some additional info you are willing to share. ... View more

Well, after working with ESRI Support and trying multiple possible workarounds we have not found a solution to allow public access to secure portal services that are using web-tier authentication.  AGOL is only able to store token based authentication such as when using portal-tier or named user authentication.  ESRI support is still looking into a possible workaround but it does not look good. https://support.esri.com/en-us/knowledge-base/faq-what-is-the-difference-between-webtier-vs-gistier-000011833 https://support.esri.com/en-us/knowledge-base/problem-the-option-to-store-credentials-is-not-availabl-000012369  https://support.esri.com/en-us/knowledge-base/problem-the-option-to-store-credentials-is-not-visible-000015387 I did create an idea to include this functionality on AGOL. https://community.esri.com/t5/arcgis-online-ideas/allow-storage-of-web-tier-credentials-to-access/idi-p/1293469 ... View more

@Todd_Metzler, You note that with SAML authentication should help resolve the issue we are experiencing.  Can you please elaborate on that a little further? We went ahead a configured our SAML identification provider with ArcGIS Enterprise and AGOL.  However, we still are not able to store a credential on AGOL to access secured services on our Enterprise deployment.  I believe SAML also does not use token based authentication to allow this to occur unless I missed something in configuring the authentication. ... View more

@RyanUthoff, Thanks for the quick reply.  I to have not been able to find anything in the ESRI documentation.  It does state that when using portal-tier authentication that SSO will not function.  However, why can not you use a domain\user to access portal items from AGOL and why do they disable the save credentials when using web-tier authentication.   I also tried making services from a AGOL-Portal collaboration public but have the same results. ... View more

Thanks, @John_Tyll  and @Scott_Tansley for your input and feedback. I ended up using the following configuration after coordinating with our IT department and ESRI Support. 1) The external.domain.com is passed through the external firewall on port 443 to the IIS server in the DMZ via NAT and a Web Application Firewall.  The IIS server hosts the Portal and server web adapters using a CA-issued certificate for the external domain.  However, the IIS server is a member of the internal domain but on a different subnet. 2) The Web Adapters were set to the external 443 port on the IIS server and configured using the external URLs https://external.domain.com/portaladaptername/webadapter  and https://external.domain.com/serveradaptername/webadapter. These are pointed to the internal Portal and Server names - https://portalserver.domain.local:7443 and https://arcgisserver.domain.local:6443. 3) We set up a Split-DNS on our internal domain for external.domain.com.  This directly directs the internal request to the IIS web adapters in the DMZ.  The external DNS directs the external IP to our network edge where the external firewall uses NAT to the internal DMZ IP. 4) We use SSL certificates from our internal domain CA on all internal ArcGIS and Portal Servers.  These were requested and installed on each server in place of the self-signed certificates.  We also added our domain CA root and intermediate certificates to these servers.  We could have added each server's certificate to each ArcGIS server, but this quickly gets complicated with multiple servers.  The IIS server is using a commercial CA for the external domain name.  5) At this point, everything was working, and we integrated Portal using IWA.  This allowed us to set up a domain administrator account on Portal before federating.  All the existing services were referenced into Portal under the domain account used to federate. 6) We chose to go ahead and federate the Portal with our ArcGIS server site.  We logged onto Portal using https://external.domain.com/portaladaptername/home.  For the Services URL we used https://external.domain.com/serveradaptername.  We have multiple ArcGIS GIS servers running on our ArcGIS Server site; therefore, the same URL was used for the Administration URL rather than one of the 6443 URLs.  I missed this requirement the first time - thank goodness for hourly server snapshots.  This does require Administration to be enabled on the server web adaptor.   https://enterprise.arcgis.com/en/portal/latest/administer/windows/federate-an-arcgis-server-site-with-your-portal.htm      ... View more