Embedded Map for HTML5 React.js with pass through service account
Let's revisit the joys and goals of Embedded "Map". To embedded in HTML5 react.js Apps for example correct? Create elements that interact with the map but are not ESRI or Geocortex based...correct?
How do we thus achieve this great goal without the requirement for a single user login and double authentication?
AKA maybe the application requires oauth, facebook, g-suite, office365, amazon cognito, etc, etc?
Seriously how do we leverage the power of the embedded "map" that uses non Portal/AGOL login credentials and elevates security UX/UI to modern day web dynamics?
-
Morning Dylan,
The common use case for using Geocortex Web for an embedded map is when there is a need for a simple map with a few simple tools that needs to appear directly in a web page and load and display quickly. Generally speaking any such application should be publicly accessible and contain publicly accessible data. Even when hosted in ArcGIS Online or an ArcGIS Portal a publicly shared application 'just works' and never challenges the end-user for credentials.
Said differently the usual concept of an embedded map doesn't involve authentication.
A few customers embed more complex maps into in-house enterprise applications where security has to be handled, and we do have experience in this area as well.
What business use case are you trying to fulfill?
Cam
0 -
Cam,
We have been building complex in house applications for various clients with Geocortex in that stack, but HAVE to avoid using Portal/AGOL security. In my humble opinion this pattern is starting to set our community backwards instead of forwards. End users want GIS, but don't need to know it's GIS. This is why MapBox, Boundless, Google Maps, etc continue to take market share of our community and degrade our role within the UX/UI of advanced non-GIS centric vs clunky siloed heavy GIS apps.
Currently the frustration is the idea of the iFrame of Geocortex for HTML5 and the load speed as well as the limitation and overhead on having react.js containers push and receive commands from the iFrame and robust 3rd party security. We have to use normally a lot of 1 way runtime paramaters from the React.js apps to push into Geocortex iFrame. We want to start achieving bi-directional interactions inside an app controlled by 3rd party B2C & B2B identity stores.
We don't want complex maps, but still want the power of the functions of Geocortex. For example we can easily embed ArcGIS for Server API, but then have to write lots of code to do simple things like layer module, map tips, etc. Our clients pay for Geocortex so why not make that more sticky through out the enterprise advanced app....that is how we are achieving GIS without the user knowing it's GIS currently.
I had very high hopes for the 5-series to achieve these goals but am getting scared the ESRI pattern is being jammed down our throats.
We use NGINX for our web server as the "Web Adapter" is garbage. So we are exploring making the Geocortex 5-Series or HTML5 Viewer open but using advanced URL firewalls via NGINX to secure it from hacktivists. We also use Auth0 for our security and are looking back into Azure's new B2C style for our 2020 plans.
I love Geocortex and have always relied on your company to think differently and push GIS in the direction the community needs it to go so I really wanted to open this up as an exploratory conversation. At first blush my excitement for 5-Series is giving me a jarring reaction on my business goals.
I am looking forward to the feedback and guidance.
Cheers,
Dylan Kennard
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
2 commentaires