OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [wsrp][security] 5/15 telecon agenda; *** NEW CONFERENCE CODE***

Note the new conference code for this and future security telecon's:

Time:  8:00 a.m. PST(11:00 a.m. EST, 5:00 p.m. CET)
Reservationless-Plus Toll Free Dial-In Number: 877.450.3529
Reservationless-Plus International Dial-In Number: +1.706.679.6653
Conference Code: 4254674195

I'd like to focus tomorrow's call on access control issues.  We talked last
time about the idea of portlets exposing roles they understand, where roles
drive levels of service access to the requestor.  We also discussed the
notion of  portals providing binding of users to roles.  Some questions to

1.  What are common scenarios for roles?  Seems like (user, admin) is the
most common scenario.
2.  Do we need to support the concept of roles in WSRP?  I believe the
answer here is yes, but would be good to discuss.
3.  Are portlets required to support roles?  I would think not required.
4.  If a portlet exposes roles, is a portal required to understand them?
5.  If the answer to above is yes, can we define a standard set of roles to
make it easier for portals and portlets to implement?

 <<wsrp security minutes 5.8.htm>>  <<wsrp security minutes 5.1.htm>>  
<<Security requirements0.1.htm>> 

Attachment: wsrp security minutes 5.8.htm
Description: Binary data

Attachment: wsrp security minutes 5.1.htm
Description: Binary data

Attachment: Security requirements0.1.htm
Description: Binary data

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC