Supermarket needs a cli option to flag a user as being able to upload.

[thomascate]

Currently a user needs to log in to the UI and click a box to enable uploads. However if the chef-server being used for auth is using ldap and the user is a local user, they cannot log in to check this option. This happens when someone tries to link delivery to supermarket and the delivery user doesn't exist in ldap.

Currently the workaround is to disable ldap on the chef server, login, click the box and then reenable ldap on the chef server. It would be useful for there to be a cli option in supermarket-ctl where an admin could do the same action as the user clicking the box.

[robbkidd]

@thomascate Thanks for reminding me of this previous conversation we had. I must admit, though, I can't think of what box needs checking in either Supermarket or the associated Chef Server account to enable uploads. Can you help me out with answering a few questions?

• Can you get specific with what URL displays the form with the box to click?

• What is a "local user?" Does that mean the user principle exists in the Chef Server directly and not in the associated LDAP store?

Also, to review the workaround steps ...

Currently the workaround is to disable ldap on the chef server, login, click the box and then reenable ldap on the chef server. {emphasis added}

The interactive act of logging in to Supermarket through the web UI for the first time is what makes Supermarket aware of the existence of a user. As of this writing, there is no other way to create an account in Supermarket other than the human-required OAUTH permission negotiation. Were we to create a supermarket-ctl command to change a setting a user—whatever the checking of a box does—you would still need to do all but the "click the box" step of the current workaround.

Is the goal of this issue is to avoid needing to manually login to the web UI for the creation and configuration of a service account (e.g. the delivery user)?