nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Permitir Federação do ArcGIS Server com ArcGIS Online

PF1

<\/HEAD>

Por favor, considere permitir a federação do ArcGIS for Server com o ArcGIS Online. Temos muitas implantações locais do ArcGIS Server usando autenticação baseada em 'token' ou 'web-tier' (Autenticação Integrada do Windows da Microsoft). Para conteúdo 'protegido' hospedado publicamente, estamos nos esforçando para migrar para o uso de logins corporativos com SAML para integrar nossos repositórios de identidade corporativa e resolver a Autenticação de Dois Fatores (TFA). Atualmente, a única forma de integrar com SAML em um ArcGIS Server é federá-lo com um produto "Portal for ArcGIS" (ArcGIS Online local). Embora tecnicamente isso seja viável, estamos enfrentando dificuldades para gerenciar dois portais públicos: um para conteúdo hospedado na nuvem (ArcGIS Online) e outro para conteúdo hospedado localmente (ArcGIS Server). Gostaríamos de expor nosso conteúdo local ao nosso portal ArcGIS Online (via federação de servidor) para que possamos usar apenas 1 portal e atender aos requisitos para integrar com SAML. A experiência do usuário ao alternar entre portais (do ArcGIS Desktop e Collector for ArcGIS) não é intuitiva para os usuários finais. Obrigado!<\/P><\/BODY><\/HTML>

Encontre mais publicações marcadas com

Status: Abrir

Comentários

BillFox

Good idea,

As of now I think you can do a hybrid with a public facing ArcGIS Server in the DMZ.

secure the publishing folder with built-in user name/password
share the secure service of your on premise enterprise geodatabase feature class to AGOL and use option to save user name/password with the service
SAML AGOL to your AD
add AD users to AGOL, groups, etc.
but editor tracking from AGOL will probably post the built-in user instead of the SAML one
on premise portal would post the correct AD user

-Bill

MikeDahm

Are there any updates on this? We have several municipal clients that use ArcGIS Server and ArcGIS Online and saving the credentials to Online makes all edits show as the saved credentials. They are smaller municipalities that rely on us for their GIS needs. Adding Portal to their deployments just isn't feasible right now. Having users login multiple times (once to AGOL and once to the layers) would be a real pain for field crews and less technical personnel. It also becomes a problem with users needing to remember 2 different accounts and passwords. Being able to properly utilize editor tracking from their SQL database and ArcGIS Server through ArcGIS Online would be a huge help.

SzymonPiskula1

What if you registered some of Server services in AGOL storing the credentials? They would then only have to log in to AGOL. Credentials would be stored in the item once registered:

ArcGIS Server web services—ArcGIS Online Help | ArcGIS

MikeDahm

That is the process we currently use but the editor tracking then uses whatever saved credentials for that services for all creation and last edited by. You can't tell who was logged into ArcGIS Online to do the edits. So if you have 5 users that are setup through ArcGIS Online to access a feature layer that has stored credentials all of their edits will show the stored credentials as the editor or creator of features.

Anonymous User

OK silly question here. I'm trying to set up Portal and slowly get in to Pro.

It appears if I enable licenses for Pro for our Portal, that if I for example take my laptop out of the building to another network, it won't work. Now, I could go into the manager and re-license to AGOL. But that's hassle and also some users don't have ability to do that themselves. Is the idea of this thread to allow for one credential, which would work for both simultaneously? That would be good. Until then I think a lot of large entities will hit this roadblock and simply wait on Pro for this to be implemented. This is one of those things where at first I was just hoping I wasn't understanding it right but I think it is designed this way currently. This mirrors the issue of publishing directly to Server from Pro in that it's an important design concept and issue.

Participe da Conversa

Faça login para publicar, seguir conteúdo e mais. Novo aqui? Registre-se gratuitamente.