Is Distributed Collaboration the correct workflow for external access to services?

[tigerwoulds]

We have a 10.7 Federated Environment set up. We are looking for a way to publish feature services and have an external client edit those services. Right now the data is in a SQL Server 17 database and our Portal uses Windows Active Directory as our Identity Store.

Our client has an instance of Portal set up and we are trying to avoid creating an External Window Active Directory account for them if possible. If we use Distributed Collaboration, can they access and edit the services without needing a login account for our Portal?

Thanks

Tiger

[tigerwoulds]

Derek Law‌ Any ideas? Sorry for calling you out so frequently! You seem to have all the answers or can point me to someone that does.

[RachelSears]

Hello Tiger Woulds‌,

Yes, the Host Portal (you) will be able to send content to the Guest Portal (the client), and receive content back from the Guest Portal (if send and receive is enabled), but only the Host Portal can make edits to the original layer that are synchronized back to the workspace. 

The best you might be able to do within the collaboration workspace is the Host Portal sends the feature layer as a copy to the Guest Portal, the Guest Portal exports it as a new hosted feature layer with their edits, then sends the new layer back to the Host Portal through the collaboration workspace.

[tigerwoulds]

Thanks for the reply! So to clarify on your first point, Only us (the host portal) will be able to make edits on the original feature layer correct? If send and receive is enabled, will they be prompted for a login for our Portal?

I see what you're saying about exporting and making edits. We were intending on using the original feature layer in various web apps/apps so this may not work for us.

Thanks