Latest Contributions by DanielUrbach

Hello Jose, You can set the recycling time for the service to be at 5:00 AM, this will restart the service. In Server Manager > Service > Edit (the pencil button) > Processes -Danny ... View more

Richard, There are various browser plugins you can use to view the SAML response coming back from ADFS to ensure the nameID parameter is indeed being passed and looks correct. For Chrome, I recommend SAML Message Decoder (SAML Message Decoder - Chrome Web Store ), for FireFox, SAML Tracer (SAML-tracer – Get this Extension for Firefox (en-US) ) Are you using encrypted assertions in ADFS?  If so then these tools won't really help as the assertion will be unreadable.  If possible, turn off encrypted assertions for the relying party set up for your AGOL organization in ADFS and test signing in again.  If it works then it could be an issue with the encryption (or likely the decryption on the AGOL side). -Danny ... View more

Richard, This might be what you are looking for: Install options—ArcGIS Pro | ArcGIS Desktop  -Danny ... View more

Sovan, You will be able to add published services from 10.6.1 ArcGIS Server as items to the 10.7 Portal. Federating that server to the 10.7 Portal would not work as the versions of both would need to be the same. Hope that helps! -Danny EDIT:  Federating the server will work, but you will not be able to set it to a specific role, such as Hosting, Geoanalytics or Raster Analytics ... View more

Cathy, If I understand what you are asking, you want to know if you can limit the users who can sign in using SAML to your ArcGIS Online organization based on their membership in a particular AD group? I would say the easiest way to accomplish this would be on the ADFS side of things using an Access Control Policy.  See the following Microsoft doc on this: Create a Rule to Permit or Deny Users Based on an Incoming Claim | Microsoft Docs  -Danny ... View more

Jack, Looks like a bug on that page.  I have reported this internally so hopefully it will be resolved soon! -Danny ... View more

Robert, ArcGIS Server 10.4.1 supports a maximum Red Hat (or CentOS in your case) version of 7.2.  See the following system requirements page: ArcGIS 10.4.x for Server system requirements—ArcGIS for Server system requirements | ArcGIS Enterprise  This may not be the issue, but I believe the "maximum OS version" is specified there because of issues with 10.4.1 at higher minor releases of Red Hat. -Danny ... View more

Meghan, ArcGIS Server 10.6.1 comes with Python 2.7 as it is needed to use ArcPy which comes with Server.  In order to use the ArcGIS API for Python you will need to install Python 3.5+ on the system you plan on using the API from.  As Joshua mentioned, check out the documentation for the various ways to accomplish this. -Danny ... View more

Joseph, Sorry to hear this is still an issue for you! Check out my post on this thread about this: https://community.esri.com/thread/216464-failed-to-create-a-site-arcgis-server-1051  As I mention there it could be related to the SSL-related settings for the user running the ArcGIS Server service, specifically not being able to use TLS 1.1 and/or TLS 1.2. -Danny ... View more

If I recall correctly, the boxes for credentials will not show up if Portal does not trust the SSL certificate for the URL provided for the service.  See Problem: The option to store credentials when adding secured services is not visible in Portal for ArcGIS  Does Portal trust the SSL certificate for tiledbasemaps.arcgis.com?  You can confirm this by using the checkURL tool like so: https://yourportal.yourdomain.com/yourwebadaptor/sharing/rest/checkUrl.jsp?url=https://tiledbasemaps.arcgis.com If it returns "success": "false", then Portal did not properly validate the SSL certificate and most likely you will need to add it to your trusted sites or add the certificate into Portal's keystore.  Any other response for that operation generally means it DOES trust the certificate and it's probably something else. -Danny ... View more

For anyone following this thread that runs into a similar error when trying to save changes in the organizational settings, please note that any users listed in the Administrative Contacts under the General tab in Settings MUST have an email address associated with the account.  If you were not sending the email attribute in the SAML response for SAML-based users and those users were previously listed as administrator contacts for your organization you will want to do one of the following: 1) Ensure that "Update profile at sign in" is checked in the "Edit Identity Provider" settings under Settings > Security, then have any users listed in Administrative Contacts sign in and confirm their profile populates the Email address value. 2) Contact Esri Support Services if option 1 does not work or you cannot change the above setting. -Danny ... View more

Alex, Glad to hear you got past that error! Because only nameID is required to send in the outgoing claims attributes, my guess is what really fixed this was simply recreating the trust between AGOL and ADFS. When did you see this issue with saving the changes?  I ask because a new release of AGOL was just rolled out in the last few days, I'm wondering if you are seeing an issue with this new release.  I don't believe the claims attributes you configured would have any bearing on AGOL being able to save the changes on that page. Can you check the network traffic in the browser developer tools when you click Save?  I'm interested to see what calls are going out and what the response to that call is. -Danny ... View more

Alex, Regarding the claims types, changing any of these WILL affect your existing SAML-based users, but only one will be a detrimental change.  Changing the attributes mapped for email, givenname or group attributes will only affect the profile of the user and potentially what enterprise-based groups they are a part of in AGOL. Changing the attribute that is mapped to nameID will actually cause AGOL to assume you are a different user!  I definitely do NOT recommend changing this unless you have a only a few users or the SAML-based users don't own content/groups.  We use the nameID to properly map your user to the AGOL named user account. To answer your last question, making changes to the claims attributes in ADFS will not require you to reconfigure the trust between AGOL and ADFS.   If you are not seeing the nameID attribute in the SAML Message Decoder but you ARE able to sign in, I'm sort of at a loss to explain that.  If you are comfortable doing so you can send me the SAML response for both the successful and unsuccessful login attempt in a private message, I'd be interested to see the difference between these. -Danny ... View more