...
Prio | Name | Story | |||||
|---|---|---|---|---|---|---|---|
| Password reset | A user that forgets his/her password wants to be able reset it using a standard email-nonce flow. | |||||
| External authentication | An administrator of a PEER instance wants to enable external authentication for PEER, overriding internal passwords for authentication in favor of an external mechanism including connecting PEER to an existing federation. | |||||
| X509 Authentication | An administrator of a PEER instance wants to enable X509-based (using smartcards) authentication, overriding internal passwords and wants a configurable method to map information present in the X509 certificate to a PEER username. | |||||
| Notification | A metadata consumer wants to be able to subscribe to notifications (eg using pubsubhubbub or XMPP) about changes to both individual entities and the full set of metadata in an instance. | |||||
| Attribute-based Notification | A metadata consumer wants to be able to subscribe to notification about changes to a set of metadata that contains a specified metadata attribute-value pair. | |||||
| Attribute access restrictions. | A PEER instance admin wants to be able to apply access restrictions to metadata attribute so that a specified (in configuration) set of attribute must only be edited by a team with elevated privileges. Such attributes must also be filtered on import of metadata. | |||||
| DNS-based domain-validation | A PEER user wants to be able to choose between a set of roughly equally secure domain validation methods including one that involves putting a TXT-record in DNS. | |||||
| Delegated domains | An administrator of a PEER instance wants to be able to allocate multiple domains (optionally including sub-domains) to a team without the need for the team to prove ownership of the domain. Such a team must then become "locked" so that only the administrator can add or remove users from the team. | |||||
| Administration team | An administrator of a PEER instance wants to designate administrator rights to a team so that all actions that can be performed as the administrator can be performed by members of that team. Such a team must then become "locked" so that only the administrator (or members of the administrator team) can add or remove users from the team. |
|
|
|
| |