Organization project with multiple developers using existing Samsung accounts has authorization issues

Hi All,
@Brad_st @erickv In our effort to jump off the Groovy IDE platform to the API model (developer mode) we have everything working except in the area of specific authorization. Under the Groovy model we have a distributed model where each hub (one Samsung account per home/hu) communicates with our server. We provide dashboards to navigate through the accounts and report the status to each other.

For the migration we use the project workspace for smartapp development and assign a lead developer as the lead administrator and assign his project to the organization. His workspace credentials are used as the administrator for the organization project. Like Groovy IDE, we can only publish in developer mode so we take our existing customer’s Samsung accounts and create a developer’s workspace for each account and assign the account to the organization through the request/approve process. Kloogy yes, but we don’t see any alternatives.

What works is that the administrator account and non-administrator accounts can see their devices and register subscriptions for device events, hub health, schedules. We can see those events and it actually works well.

What does not work is non-administrator accounts can’t query for a specific capability for devices like battery value. The administrator account can query for battery value. So its the default authorization scopes for the non-administrators that won’t allow getting battery capability attributes.

So here are the questions:

  1. Is there a way to override the default authorization scope that is assigned to the non-administrator accounts?
  2. Is there a better way to do this? Basically, without a means to publish the organizational smartapp we are limited to developer mode.

Hey, @tryagain

Yes. Check the details on the Apps API / updateAppOauth.

Unfortunately no, because the certification guidelines for the distribution of SmartApps (Automation, Connector, and API Access) have not been released yet.

Also, consider this distribution method as a Beta stage to collect feedback from your users and make the proper tweaks for when the certification process is ready.