search

sandstorm-io / sandstorm

Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
https://sandstorm.io
Other
6.75k stars 706 forks source link

powerbox identity picker has confusing error message if there are no contacts #2827

Open dwrensha opened 7 years ago

dwrensha commented 7 years ago

The error message is currently "no grains can provide the requested interface". It should instead say something about contacts and how to add them.

Originally reported by @abliss as https://github.com/wefork/wekan/issues/79.

oec commented 7 years ago

To copy the original bug-report: I have an admin-user (login per email) who can add users to Wekan-boards through the powerbox, but the other admin-user (login per ldap) - who is actually the creator of the Wekan-grain - is not able to add any users through the powerbox.

kentonv commented 7 years ago

@oec This is probably because the second user doesn't have any users in their contact list. There are two ways to add people to your contacts:

  1. Share a grain with them, and have them open the share and choose to reveal their identity.
  2. Configure organization settings, and choose "Make all organization users visible to each other" -- this will cause all members of the organization to have all others in their contacts automatically.

Note that from your description, it sounds like you might have an organization configured, but configured it to include only e-mail users. If you also check the box for "Users authenticated via LDAP", then the LDAP user will become part of the org and so will be able to see other org users in their contacts.

oec commented 7 years ago

@kentonv, thanks for the feedback. I actually do follow option 2 ("Make all organization users..." selected) and also do have "Users authenticated via LDAP" set, but still: My LDAP-user can't see any other user within the powerbox.

dwrensha commented 7 years ago

Ah, so you are hitting https://github.com/sandstorm-io/sandstorm/issues/2826 then.

kentonv commented 7 years ago

@oec Your bug should be fixed as of today's release, which you should receive automatically within 24 hours.

(The original bug that this thread is about is not fixed, however, so not closing the issue.)