Modèles d'authentification utilisateur pour une application AGOL/Portal personnalisée

Question

<\/HEAD>Je cherche à créer un outil de cartographie personnalisé pour un client. Ils aimeraient utiliser l'application standard AGOL/Portal comme point de départ et ajouter certains de leurs propres widgets personnalisés pour réaliser diverses fonctions spécifiques à leur activité (intégration avec d'autres systèmes, outils personnalisés de marquage de carte, etc.). J'ai utilisé WAB Dev. Edition pour télécharger une application test et personnaliser certains widgets, puis j'ai déployé cela sur un serveur de test interne et tout fonctionne bien. L'application test utilise une carte AGOL partagée avec tout le monde - donc aucun formulaire de connexion AGOL n'apparaît lors de l'entrée dans l'application hébergée localement.<\/P> <\/P> Ma ou mes questions concernent la création d'un système d'accès utilisateur pour cette application. Mon client dispose d'un certain nombre de comptes ESRI Named User, mais ils aimeraient permettre l'accès à leur application à potentiellement 50-100 utilisateurs internes. Ces utilisateurs auraient besoin d'accéder à plusieurs couches et pouvoir éditer ces couches. J'ai fait créer certaines classes d'entités SDE au sein de l'instance Portal locale du client (elles ont été publiées via un ArcGIS Server fédéré - donc elles ont un accès nommé utilisateur). J'ai compris comment ajouter ces couches à la carte au démarrage de l'application (en utilisant le compte named user pour authentifier les couches), mais cela signifie stocker le compte named user et potentiellement permettre à plusieurs utilisateurs d'utiliser le même point d'accès named user (ce qui, je pense, n'est pas conforme à la licence ESRI).<\/P> <\/P> Quelles sont nos options ici ? La licence ESRI permet-elle d'ajouter (à l'exécution) des couches à une carte partagée avec tout le monde ? Si oui, ces couches peuvent-elles provenir d'une base de données SDE et être publiées via ArcGIS Server ? Qu'en est-il si l'authentification standard ArcGIS Server est utilisée depuis un serveur non fédéré ? C'est-à-dire créer des utilisateurs dans l'outil de gestion des utilisateurs d'ArcGIS Server qui ne sont pas des named users.<\/P> <\/P> En gros, nous aimerions gérer l'accès utilisateur à l'application, sans utiliser le système named user. Il semble que cela soit techniquement possible, mais est-ce conforme à la licence ?<\/P> <\/P> Nous avons essayé de poser cette question à notre support local mais n'avons pas encore reçu de réponse claire.<\/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.