|
POST
|
Thanks Zachary Hart and Daniel Cota, for now we have no other recourse than to unfederate. There is light at the end of the tunnel, however, and ArcPro will soon be able to publish directly to Server as noted by Philip Heede near the very bottom of this long thread: https://community.esri.com/ideas/12258 We have been working on this deployment for many months, and it feels like defeat to roll it all back. At least we still have the power of Portal and the power of Server, albeit independently of each other.
... View more
05-23-2019
09:20 AM
|
3
|
0
|
3237
|
|
POST
|
Thank you for publishing this Zachary, we have just run into the exact same issue on our end. We have some large internal applications that will not be able to have named users, as more than 120+ users in our company will need to edit at lease some data in the apps. We have been looking for solutions and this post (with Daniel's subsequent reply) confirms our suspicions. It is not a great idea to have to make all our services public, as the whole point of upgrading was to allow for a higher level of security in our company. Therefore we are faced with with either losing all our security by opening up the services, or un-federating and going back to the old deployment. Seems like a no-win situation. Daniel Cota, can you speak more to the more functionality we would gain by continuing to have Portal federated? The Esri documentation is fairly limited and not up-to-date as far as publishing from ArcPro 2.4 (directly to Server) and some other items.
... View more
05-17-2019
03:38 PM
|
5
|
4
|
3237
|
| Title | Kudos | Posted |
|---|---|---|
| 5 | 05-17-2019 03:38 PM | |
| 3 | 05-23-2019 09:20 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-02-2021
11:52 AM
|