Is it possible to lock down the Web AppBuilders connection to an organization?

5109
15
03-18-2015 05:11 PM
DavidYarnell
New Contributor III

When a new user arrives at the Web AppBuilder (Developers Edition), they are prompted for the full URL of their portal or ArcGIS Online for Organizations subscription.  This is practical for users running the application locally, but if we’re standing this up in a shared (or potentially public) deployment, we need to be able to lock this down to our organization’s subscription, and not allow users to specify a different URL. Is there a way to control this?

Tags (1)
0 Kudos
15 Replies
RichAlger
New Contributor

What did you end up doing, Torrin? Our organization wants to do something similar.

0 Kudos
TorrinHultgren
New Contributor III

We never did get the developer edition working in anything other than a sandbox environment for "communal development", but this business case is one of the drivers towards us exploring Portal for ArcGIS. Portal's a heavy lift from a resource and management perspective, but it does offer at least a few compelling options not available in AGOL.  

Dvirus
by
New Contributor III

Torrin Hultgren‌ Did you success to manage with IISNode and WAB 2.7 a full functional WAB expericnce ?

0 Kudos
TorrinHultgren
New Contributor III

No, it's pretty clear that Esri doesn't intend to support WAB as a standalone multiuser solution and their answer to this question is a full-fledged Portal installation. We've tested that, and it works fine - if you throw enough hardware at it. But that's only for the configurator portion of WAB . If you use either AGOL or Dev Edition for an initial configuration and then dump it out for further customization, it runs fine on any web server, no need for Node.JS or any other server-side components. We do a lot of that because of our limited hosting options.

Dvirus
by
New Contributor III

Hi Torrin Hultgren‌ 

Thanks for reply.

If so, is there any point to building a settings screens for widgets?

according to that every 'save' to application the operator need to download it as zip and hosted in the IIS server ?!

What do you say about 'Hybrid' mode:

1. Host the folder C:\WebAppBuilderForArcGIS_2.7\server\apps in IIS

2. Need to change the api url at env.js file (in each app) - uncomment line 107

3. Continue to configure via the WAB SDK (Node app).

4.( after finish configure close startup.bat)

Is that make sense? or maybe there is other workflow?

The goal is to move the entire management (As much as possible) of the app to the portal interface so the operator can manage by him self most of the settings that relate to the app.

P.S

No, it's pretty clear that Esri doesn't intend to support WAB as a standalone multiuser solution and their answer to this question is a full-fledged Portal installation.

In which case you don't install the a full-fledged Portal?! How WAB SDK can work without portal?

How you will select Map? 

A Lot of widgets 'talk' with portal items.. (Add Data widget for example..)

0 Kudos
TorrinHultgren
New Contributor III

Hi Dvirus b‌,

We had been hoping for a solution where we could deploy WebAppBuilder running under Node.js, without portal, and federate it with our ArcGISOnline subscription to allow a customizable multiuser WebAppBuilder experience. That's the vision that we're giving up on because Esri's only supporting this scenario under a Portal umbrella. And while we're disappointed, we can think of some pretty defensible reasons why they chose that route, among them the concerns you raise.

To your first question - adding a settings screen for widgets is probably more helpful to those running WAB under Portal than those running standalone WAB - mostly because the latter are likely to be developers who skip past GUIs and go straight to config files. But it's still a best practice. Hope that helps.

0 Kudos