APP ID: Deploying VS web on-prem with multi server

Mike Diss-Torrance

30. September 2022 21:58

I'm just trying to get my head around the deployment sequence and who needs to be involved and what steps they would be engaged. I just need to write this out and perhaps you can confirm/correct any of this.

First off, while I'm both an admin and developer, I'm trying to design this for other developers too. For the outline below, Alex is an Administrator who installed the VS designers in Development and Production. He used his admin account. Dan is a Developer who built a VS web application and want to deploy it to production.

In order to deploy an web app from DEV to PROD (on prem. portal environments), Dan needs to provide:

• Vertigis Studio Web Location (production URL of web designer)
• Portal URL  (production URL of portal)
• App ID

For the App ID, it seems Dan needs to use the App ID associated with the VS designers (Web, workflow, etc.) that were install in production (i.e. Alex's account).

When Dan ran the "deploy to production" step, the resultant Portal items are copied into Alex's admin account. While Dan can continue to make changes to the application and re-deploy it to production, he cannot access the production Portal items themselves, including changing it sharing permissions. 

At that point, it would seem that Alex would then need to log into the production portal, change the ownership of the items to a generic agency account, including assigning the proper sharing permissions (i.e. share with Organization or Public). 

Is this correct or have any recommendations?

 

P.S. My name is Mike. 

-1

• 

  Cam Barnard

  5. Januar 2023 17:13

  Hey Mike - seems like you have most of it correct.

  In general the first time you push an app to a new environment it is created unshared, and you must adjust those permissions (which are remember when you do subsequent deployments).

  Only one part of the description I'm unsure about. When Dan deploys the app from dev to prod (using the App ID setup for Oauth) he will be prompted for credentials to sign into the production portal. Assuming he signs in with his own credentials, I would have expected the production items created to be 'owned' by Dan.

  App deployment aside - all users are signing into an Esri portal against an app ID supplied for Oauth ... but when they save/create items they are owned by the user that signed in.

  What is the sharing on the App ID for Oauth setup on the Production Esri portal? 

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.