Patrones de autenticación de usuario para la aplicación personalizada AGOL/Portal

Question

Estoy investigando la creación de una herramienta de mapeo personalizada para un cliente. Les gustaría usar la aplicación estándar AGOL/Portal como punto de partida y agregar algunos de sus propios widgets personalizados para llevar a cabo varias funciones específicas del negocio (integración con otros sistemas, herramientas personalizadas de marcado en el mapa, etc.). He utilizado WAB Dev. Edition para descargar una aplicación de prueba y personalizar algunos widgets, y luego he desplegado esto en un servidor de prueba interno y todo funciona bien. La aplicación de prueba usa un mapa AGOL que está compartido con todos, por lo que no aparece un formulario de inicio de sesión AGOL al ingresar a la aplicación alojada localmente.<\/P> <\/P> Mi(s) pregunta(s) se relaciona(n) con la creación de un sistema de acceso de usuario para esta aplicación. Mi cliente tiene varias cuentas ESRI Named User, pero les gustaría habilitar el acceso a su aplicación a potencialmente 50-100 usuarios internos. Estos usuarios requerirían acceso a varias capas y poder editar estas capas. He creado algunas clases de entidades SDE dentro de la instancia local Portal del cliente (han sido publicadas a través de un ArcGIS Server federado, por lo que tienen acceso mediante Named User). He descubierto cómo agregar estas capas al mapa cuando la aplicación se inicia (usando la cuenta Named User para autenticar las capas), pero esto implica almacenar la cuenta Named User y potencialmente permitir que múltiples usuarios usen el mismo punto de acceso Named User (lo cual creo que no está conforme con la licencia ESRI).<\/P> <\/P> ¿Cuáles son nuestras opciones aquí? ¿La licencia ESRI permite agregar (en tiempo de ejecución) capas a un mapa compartido que está compartido con todos? En caso afirmativo, ¿estas capas pueden provenir de una base de datos SDE y ser publicadas a través de ArcGIS Server? ¿Qué pasa si se usa la autenticación estándar de ArcGIS Server desde un servidor no federado? Es decir, crear usuarios dentro de la herramienta de gestión de usuarios de ArcGIS Server que no sean Named Users.<\/P> <\/P> Básicamente nos gustaría gestionar el acceso de usuarios a la aplicación sin usar el sistema Named User. Parece que esto es técnicamente posible, pero ¿cumple con la licencia?<\/P> <\/P> Hemos intentado plantear esta pregunta a nuestro soporte local pero hasta ahora no hemos recibido una respuesta clara.<\/P><\/BODY><\/HTML>

EugeneLamnek · Answer

Thanks, I will look at the video and the pdf.

In our case all users will need to edit, but some of them will only edit infrequently, so level 1 may not be suitable.

Also, another reason for us looking at other authentication methods is we want to provide integration with a non-spatial web application that operates within the clients organization. By integration, I mean things like: user clicks on a spatial feature on the map, which triggers a call to a web service that goes off and finds matching records from the non spatial application based on spatial ID of the feature and returns the matching record(s) which then gets displayed in a custom widget. The existing non-spatial app has its own system of user, roles, groups etc. so we were hoping to be able to use this for the hosted web app, rather than maintaining two systems of users (one owned by non-spatial app and the other being Named Users).

XanderBakker · Answer

Hi Eugene Lamnek ,

'You can however (as far as I now) add layers on the fly on a Web App that is published on a local web server.'

By local web server, do you mean a web server on the internet as opposed to having the app running from AGOL/Portal?

And do you mean, you can add layers that require authentication, as long as the map is not publicly shared?

It can be a web server inside your own infrastructure or in the cloud, accessible from outside your organization or only available inside your organization. If you download for instance a template application you can modify it or use for instance Web AppBuilder for ArcGIS (Developer Edition) | ArcGIS for Developers . What you cannot do is configure an application in ArcGIS Online and share it publicly and consume content that is not publicly available. If you create a webmap in ArcGIS Online and share that publicly, it cannot contain services that are only available behind your firewall. If you add those layers on the fly, the web map on ArcGIS Online will not have any layers that are not publicly available.

With your second point, I understand sharing named users is not allowed. But (my knowledge is limited on this because I haven't tested it) if you are loading layers from a non-federated ArcGIS Server, they would not need to be authenticated by the named user and so no named user sharing would take place??

That may be the case, but if you are going to implement ArcGIS Enterprise, the base deployment (Server, Portal, DataStore and WebAdaptor) will require Federation between the ArcGIS Server and Portal. I think I read this in the slide notes from the presentation on Architecting Your Deployment: See video here: ArcGIS Enterprise: Architecting Your Deployment - YouTube

I will CC Philip Heede hopefully he can clarify this for you.

There is also a great document that might be interesting to read (updated last month): https://www.esri.com/~/media/Files/Pdfs/products/arcgis-platform/architecting-the-arcgis-platform.pdf

Third point, I agree that the named user system would work well, but as the system grows, from what I understand, large costs are involved in having so many named users, many of which may only access the application very infrequently

From "architecting-the-arcgis-platform.pdf ": An ArcGIS Identity is managed as a named user credential within the platform. This credential is used to sign into any app, on any device, at any time, and to provide access to all maps, apps, data, and analysis a particular user is entitled to. As users sign into the ArcGIS platform with their named user credentials, their identity gives them access to authoritative data, GIS capabilities, shared content, apps, and their saved maps and items. The named user model allows an organization to securely and appropriately extend the reach of its geospatial capabilities to everyone who needs them.

So by implementing the named user model, you avoid developing some access to data and applications and you probably miss out on some really good stuff. There are two levels of named users. As far as I understand from your explanation, you will have many users that will simply use the application but not create any content. Those users can use a named user of level 1 which is about 1/5th of a level 2 named user.

EugeneLamnek · Answer

Thanks for your comments. Not sure what you mean by your comment:

'You can however (as far as I now) add layers on the fly on a Web App that is published on a local web server.'

By local web server, do you mean a web server on the internet as opposed to having the app running from AGOL/Portal?

And do you mean, you can add layers that require authentication, as long as the map is not publicly shared?

With your second point, I understand sharing named users is not allowed. But (my knowledge is limited on this because I haven't tested it) if you are loading layers from a non-federated ArcGIS Server, they would not need to be authenticated by the named user and so no named user sharing would take place??

Third point, I agree that the named user system would work well, but as the system grows, from what I understand, large costs are involved in having so many named users, many of which may only access the application very infrequently.