Manual approval required for update when disabling authentication

Hi,

I’m considering to disable authentication (jwtnone) in an existing connect app.

For historical reasons the app has authentication enabled, but it’s not needed anymore (and unlikely that it will be needed in the future). The backend is only processing the lifecycle events and maintaining a tenants DB. It never requests any data from the host instance.

To simplify the introduction of data residency support I’d like to drop the backend, making it a static app.

The app also has read and write scopes for usage by AP.request. These scopes won’t be changed.
Furthermore the app has licensing enabled, and this will be kept as well.

Question: Will this change in the authentication field (and removal of the lifecycle endpoints) require manual update approval by administrators or will the update be installed automatically?

Thanks!

5 Likes

Hi @jens,

I don’t think this change will necessitate manual upgrade approvals. From memory, the changes that require approvals are:

  • Change of payment model
  • Increase of scopes
  • Change of baseUrl.

Regards,
Dugald

cc @chparker

3 Likes

@dmorrow , @jens that sounds about right, yes.

Cheers,

Chris

2 Likes

I don’t think that change of baseUrl requires manual approval, since I have done this a couple of weeks ago and it updated automatically.

3 Likes