Internal ONLY Web Map Sharing Issues

[BrianO_keefe]

So we have a webmap that is INTERNAL ONLY. We have to build the 'ArcGIS' map side online, then using WAB build the web map, prop it up on our internal server, and now it's asking for AGOL sign on. This is supposed to be used by Field Crews?! They will 'never' have AGOL accounts... what is the proper workflow for a situation like this?

[BrianO_keefe]

Yes it is.

I've read everything I can get my hands on. Nothing even shows this error I'm getting?! It's really frustrating. I try to avoid filing a ticket whenever I can because if I can find the answer it sticks in my head better that way...  but ugh. I'm about to make a call...

[AhjungKim4]

"The big thing about step 3 is that the item is PUBLIC (the app item that you are registering). The webmap is still private and secured though."

This is a false statement.  By making your app registration information public, you are basically sharing your appID and secret with everyone.

[RobertScheitlin__GISP]

Ahjung,

   I think you are misunderstanding that as me saying that I am sharing the app registration item to the public.

[BarnabyRockwell]

Hi Robert,

For some reason, this proxy method no longer works for a local WAB Dev 2.4 app which calls an AGOL WebMap.  I now get just a blank (white) page in the browser.  Any ideas?

Cheers,

Barnaby

[RobertScheitlin__GISP]

Barnaby,

   I will look into this and reply to your other thread once I get 2.4 and do some testing.

[BarnabyRockwell]

Thank you, Robert!  🙂

[JeffSauder]

Hi Robert,

I am getting something similar to what Barnaby is getting (white screen, frowny face error), do you have a link to the other thread you are referencing here?

Thanks,

Jeff

[RobertScheitlin__GISP]

Jeff,

  Sure here it is:

https://community.esri.com/thread/192503-net-proxy-setup-no-longer-working-for-wab-dev-24 

[DavidColey]

Hi Jeff - something else to look for when you get the frowny-face error.  For me that will happen when I leave out a closing brace or bracket, or a missing comma in the config as I paste in my rules array from previous builds.  Also, in reading through the thread Robert references below, it's not so much an issue with WAB 2.4 and the proxy as it is with Chrome at 58.x.  Chrome doesn't like mixed http / https references. 

[JeffSauder]

Hi David,

Thanks for the reply. I did check (multiple times) the closing bracket thing, that is something that has always plagued me too with javascript. I put the file in an IDE editor, that shows any mistakes like that, and all looked good. I have also had ESRI support look at these as well.

I did put the https: back in for all the urls, not just the agol ones.

Thanks,

Jeff