Allow a configurable set of principals to successfully authenticate.

[dubacher]

As a controller of a satellite, I want the ability to configure one or more principals who are authorized to successfully log in to a Dapp.

Acceptance Criteria:

• In the Juno console, the controller can manually define the principals that are permitted to log in to the Dapp.
• The controller can generate invitation URLs that allow new principals to be automatically added to the list of authorized principals.

[peterpeterparker]

Hi @dubacher,

I’ve implemented a new configuration option for authentication that allows you to define a list of identities/principals permitted to sign in and use any features of the datastore or storage (taking precedence over all existing rules).

This configuration can be applied either after users have signed in — for example, you share your app link with a few people, they sign in, and then you add their principals to the list — or beforehand — where you e.g. set your own principal as the only authorized user to disallow any other sign-up, share the app link, and display an option for users to view their principal after a failed sign-in attempt. They can then send you their principal, and you can gradually add them to the list.

Regarding the second part of your description — generating invitation URLs — I’d prefer not to implement that for now, as it would require more work and additional security considerations.

Does that work for you?

---

Screenshots:

[dubacher]

Hi @peterpeterparker. Thanks for considering my feature request. The specification meets my current requirements.

[peterpeterparker]

Great to hear, thanks for the feedback! I prepared the documentation and will then ship this in the next version (within next weeks). I close this feature request as complete but, feel free to ping me anytime for refinement and improvements. Thanks for sharing the idea!