Latest Contributions by AlexStevenson

This particular case (other installation in the background) has happened to me several times.  I would first recommend a reboot and try to reinstall. ... View more

Hi Kelly, We have confirmed that we can add the Navigator license during the workflow as long as we are not adding the member using their enterprise login. With the enterprise login method, we can select the Group(s) we would like to add them to but seem to be missing the Add-On licenses tab as shown below: Thanks, Alex ... View more

Awesome - Thank you, Kelly!   ... View more

Hi Kelly! Now that the AGOL version update has been rolled out, how can we assign Navigator licenses as part of the member invitation process?  Currently, it's a bit of an administrative burden to send our users an AGOL invitation link, wait for them to accept it, then have them let us know that they accepted the link (or hear about issues when they try to log into Navigator on their mobile device) to which we can then assign them a Navigator license.   Thanks! -Alex ... View more

Danny, We saw the issue happen Wednesday morning.  I believe that the new release for AGOL did not happen until Wednesday evening but the timing of these issues is peculiar.  I did capture the network traffic in the browser developer tools and saw the following, which was interesting: I also tried saving under a non-Enterprise account and received the same response error. Side note - I tried sending you a direct message with some more information but I'm not allowed to it seems. -Alex ... View more

Danny, We have a case open with premium support and it was determined that we needed to add the other LDAP attributes to the outgoing claim types.  So, I worked with our ADFS admin to add these.  We did not change the mapping of the User-Principal-Name to Name ID.  We also re-established the trust between AGOL and our network (imported the federation metadata xml).  Also, that SAML Message Decoder extension has been working great.  I can now see the attributes in the SAML response header. After making these changes, we have not seen the IDP error come back just yet.  However, a new issue came up. Now, when trying to hit the Save button in the Organization Settings, it throws an Error saying that it is unable to save our settings at this time.  Premium support is thinking that it has to do with the newly added LDAP attributes affecting the way AGOL is trying to save or a corrupt metadata file.  The next test is to Remove Enterprise Login and test if we can Save.   Regards, Alex ... View more

Hi Danny, I'll also be using the SAML Message Decoder.  Thanks for mentioning it! I checked the Edit Identity Provider settings and it appears we do not have Encrypt Assertion enabled.   I'm checking with our ADFS admin to make sure we are including the 4 User Attributes for outgoing claim types as mentioned in the article you mentioned. A couple of questions on this - if we make a change to the ADFS mapped attributes, say that attributes are added, will that affect the existing SAML-based users in AGOL?  And, will that require an update with our IDP? Thanks, Alex ... View more

Hi Daniel, Thank you for the response. I don't have Firefox but I did see that there's a SAML Tracer for Google Chrome.  I installed that extension, logged out of AGOL and logged back in.  No issues this time around with logging in.  I looked at the SAML extension logs but did not find any attribute with "Nameid" or "Name_ID" in the response data tab.  I also exported the SAML logs (it exports as a .json file) and did a search in there for NameID but it didn't return anything. I have confirmed that this is happening to other users as will and with the mobile app Navigator for ArcGIS. Thanks, Alex ... View more

Thanks, Jonathan.  We made the change to the scheduled reboots and I haven't seen the issue in the logs since then. ... View more