app/service grant authorisation

[xmasclaux]

A partner created an app dedicated to cultural actors from an Ozmarue model This service (Cartographie CLDD Diois) is now accessible by the store : https://portal.ozwillo.com/fr/store/service/03b6365d-bf21-4a9c-93bd-d25e6509eb57 When an user install it, the grant authorisation is called Ozmarue It could be better if service name (Cartographie CLDD Diois) ask for authorisations.

[tbroyer]

What appears here is the name of app instance, because authorizations are granted per-instance, and not per-service. The initial design of the platform was that app instances would be named by the user at the moment he instantiates them. That was finally changed, or maybe just never done; anyway the name, description and icon are currently set by the Portal, as a copy from the application (and only for the locale of the current user), and cannot be changed afterwards.

We have to decide who sets those information, when, and from where:

• either at instantiation time on the Portal, as originally designed, but requiring an additional step for the user. It could later be changed from the Portal too (as is always possible for services).
• or at provisioning time by the app factory (possibly based on information from the buying user and/or organization). It could later be changed from within the application; possibly from the Portal too (as is always possible for services).
• or possibly a combination of all the above; or maybe set at instantiation time (by the Portal or the Kernel) as a copy from the application (as currently, maybe preserving L10N though), but with a way to later change the values.

We had been discussing something similar lately on a private issue (pole-numerique/oasis#121), about slightly changing the endpoint used by the Portal to instantiate an app to have the Kernel copy those values from the application (rather than expecting the Portal to provide them). Depending on what we choose above, this could come in contradiction to what we were discussing. /cc @ilucatero

Anyway, there needs to be a way on the Kernel side to update those values, that currently doesn't exist. And we'll then decide whether that should be possible only from the Portal or not (it'd be possible only for app_admins anyway). There then needs to be other changes elsewhere too (Kernel, provisioning protocol, and/or Portal) to properly initialize the values, and to call the new API.