Solved! Go to Solution.
Great Question.
It is a Mix, some are bit.ly's and some are https://uwsupplemental.maps.arcgis.com/apps.................
A mix of both worked and one bit.ly didn't, one https:// didn't.
It appears that some of the Maps as Apps provide a 'bit.ly' option whereas others do not, hence the https: versions.
It is great to discuss this, I greatly appreciate the questions and back/forth.
Regards,
Greg
I have checked and it looks like we have "Allow Anonymous Access to Your Organization" checked, but I am still having this problem as well.
I tried to verify that we are also making these other items public as described in the picture above. It is very frustrating to have public maps requiring a sign in. It basically makes them useless.
Also, this problem is not always constant. I often don't have to be logged in on my own computer to get to the maps, so I assume it's working. Then I get complaints from others. Could it be related to cookies? I seem to recall that working for me one time in the past. I had my co-worker clear his cookies and try again and it worked. Another way I used to be able to get around this was to have people go to arcgis.com and search for the map and for some reason they wouldn't get a prompt to sign in if they did it that way. However, I tried that yesterday and it didn't work. The maps and the apps came up and began loading and then jumped to the sign in screen.
Can I also say that I am often frustrated with the sign in system for all of this. I can't get it to "remember me" When I am doing work on our maps, I have to sign in over and over. The only way I can find to get it to keep me logged in is to duplicate the browser tab I am working in before I attempt to navigate somewhere else in the AGOL realm. Very frustrating!
Here are some of the maps I'm having trouble with.
I think you are correct. I wasn't thinking this was my problem, but nothing else was working. So I went to the web map in My Content and opened the sharing information to make sure it was shared publicly. It was shared publicly, so I hit save and was going to move on to keep trying to find the issue. That is when I got the prompt to correct the share setting on one of the layers I had recently updated. I gave it the okay to correct the sharing and things are working again. I think the layer I updated was in fact shared publicly, but either way, this solves the problem. So I recommend that if you are having a public map that is requiring people to sign in, go in and "share" it publicly again and see if you get the prompt. Whether is corrects the sharing of layers that aren't yet shared publicly or resets a glitch from updates you've made, it gets it all public facing again. (Just for good measure I went through my other maps and re-saved their share settings, it may be a good step to add to your workflow whenever you update a map.)
Out of curiosity, are the maps that the public is able to access being accessed through a URL like http://www.arcgis.com/home/webmap/viewer.html?webmap=927b5daaa7f4434db4b312364489544d
or
http://<your organization>.maps.arcgis.com/home/webmap/viewer.html?webmap=927b5daaa7f4434db4b312364489544d
I've also noticed that you cannot add www. to the beginning of your organization's web address. That causes issues. i.e. wsdot.maps.arcgis.com/home works, but www.wsdot.maps.arcgis.com/home does not.
Heath
Great Question.
It is a Mix, some are bit.ly's and some are https://uwsupplemental.maps.arcgis.com/apps.................
A mix of both worked and one bit.ly didn't, one https:// didn't.
It appears that some of the Maps as Apps provide a 'bit.ly' option whereas others do not, hence the https: versions.
It is great to discuss this, I greatly appreciate the questions and back/forth.
Regards,
Greg