Consolidated Requirements Document

From OpenLiberty.org Wiki

Jump to: navigation, search

According to the ID-WSF 2.0 Marketing Requirements Document, we must:

1. Provide a means by which a web-services consumer (“WSC”) can request a service interface specification (“SIS”) resource belonging to one “Principal” (as defined in the ID-WSF specifications) on behalf of another.

2. Provide a means by which a WSC, for a particular Principal, can determine the location of the SIS resources of those Principals who have authorized that Principal to access those resources.

3. Provide a means by which a WSC can discover the network location of a given Principal’s list of “friends” (as maintained at his/her identity provider).

4. Provide a means by which a Principal, when visiting a WSC, can manage his/her list of friends stored elsewhere (e.g., add new friends, delete existing friends, etc.).

5. Provide a means by which a Liberty WSC can subscribe to data regarding some resource at a WSP.

6. Provide a means by which a Liberty WSC can notify WSCs who are subscribed to receive change notifications, subject to the corresponding privacy policies that apply to such resource.

7. Provide a means by which a WSC can query subscriptions linked to some resource.

8. Provide a method by which a WSC can cancel his/her subscription for notifications.

9. Provide a method by which a web-services provider (“WSP”) may inform a WSC that it is canceling a subscription.

10. Provide a method by which a WSC can update a subscription.

11. Provide a means by which a Liberty WSC can specify the endpoint that should be receiving notifications (if different from the WSC’s application endpoint).

12. From ID-WSF 2.0 SCR

According to the ID-WSF 2.0 Static Conformance Requirements document, the WSC must support the following:

13. WSC "common features"

14. SAML SP SOAP binding

15. SAML SP WSC security mechanisms

16. LUAD (LUAD WSC)

17. SAML DS bootstrap

18. Authentication service (LUAD)

19. Service discovery

20. Service invocation

Additionally, we should strive to include support for:

21. Single sign-on (“SSO”) service

22. Group & user management

23. Invitations

Personal tools