I am trying to set up an Enterprise to Enterprise Distributed Collaboration to allow another agency to edit my data, but it doesn't seem to work, and I'm not sure if it is a software limitation, or if it is a setup issue.
Scenario
Enterprise A has published feature layers with Branch Versioning enabled that are stored in an Enterprise GDB and published as references. Enterprise A hosts a Distributed Collaboration with Enterprise B as a guest.
When Enterprise B tries to access the feature layers, it prompts them to sign in to Enterprise A. If you enter the credentials to sign into Enterprise A, this works fine - however, A doesn't want to B to be able to sign into their Enterprise, they only want them to access the shared data.
Enterprise A then stored the credentials in the Workspace so that Enterprise B users could just pull in the layer without typing their username/password- however, since you are limited to storing "viewer" credentials, Enterprise B is not able to edit the layers due to permissions issues (the fact that the account is just a viewer)
Ultimate Question
Is there a way for users from another Enterprise to edit data in my Enterprise, using a Branch Versioned Feature Class without having to give them direct access to my portal? Any help is appreciated.
Additional note: A copy distributed collaboration won't work as it does not copy over or enforce the attribute rules and data integrity requirements.
