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

 


Help: OASIS Mailing Lists Help | MarkMail Help

id-cloud message

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


Subject: Re: [id-cloud] Pending JIRA issues



Here are the texts.  All use cases need service/actor normalization, fully developed process flows and eliminate remaining "TBDs" as well besides any other items listed specifically in JIRA issues.




Use Case 13 "Transaction Validation and Signing in the Cloud" (SafeNet) - Remove if Author Agrees
Created: 15/Sep/11 12:51 PM   Updated: 15/Sep/11 12:51 PM  Due: 30/Sep/11




Component/s: UseCases
Affects Version/s: None
Fix Version/s: None



General Normalization needed (to approved actors and service name types) needed if preserved.

Use Case 13: "Transaction Validation and Signing in the Cloud": TBD, perhaps reflect specific goals of the 3rd use case scenario, Doron asked that we remove in favor of PrimeKey use case. Is this still his wish?





Use Case 11 ": "Enterprise to Cloud SSO" (SafeNet) - Use Case Cleanup/Normalization
Created: 17/Aug/11 10:05 AM   Updated: 15/Sep/11 12:51 PM





Component/s: UseCases
Affects Version/s: None
Fix Version/s: None


Gershon Janssen: AI Use case 11, 12, 13: Doron (SafeNet)


General Normalization needed (to approved actors and service name types) needed.

Use Case 11: "Enterprise to Cloud SSO": This use case (along with the portion of Use Case 10 and Use Case 12 all originally from SafeNet), are perhaps specific scenarios of use case 6 "Federated SSO and Attribute Sharing". Another comment was this could be a scenario of use case 19 "Access to Enterprise's Workforce Applications Hosted in Cloud". It was suggested that we, at some point, list related use cases.




Use Case 12 "Consumer Cloud Identity Management, Single Sign-On (SSO) and Authentication": (SafeNet) - Cleanup/Normalization
Created: 15/Sep/11 12:45 PM   Updated: 15/Sep/11 12:52 PM  Due: 30/Sep/11



Component/s: UseCases
Affects Version/s: None
Fix Version/s: None



General Normalization needed (to approved actors and service name types) needed.

Use Case 12: "Consumer Cloud Identity Management, Single Sign-On (SSO) and Authentication": Same comments as Use Case 11. That is:

>> This use case (along with the portion of Use Case 10 and Use Case 11 all originally from SafeNet), are perhaps specific scenarios of use case 6 "Federated SSO and Attribute Sharing". Another comment was this could be a scenario of use case 19 "Access to Enterprise's Workforce Applications Hosted in Cloud".

>> It was suggested that we, at some point, list related use cases if we preserve multiple use cases with same general scenarios



Please make ur edits against the Rev 2 draft in Kavi document area using the MS Word feature "track changes" so I can merge and preserve document styles.

Thanks,
Matt




From:        "Cohen, Doron" <Doron.Cohen@safenet-inc.com>
To:        Anil Saldhana <Anil.Saldhana@redhat.com>, Matt Rutkowski/Austin/IBM@IBMUS
Cc:        "id-cloud@lists.oasis-open.org" <id-cloud@lists.oasis-open.org>
Date:        10/03/2011 08:02 AM
Subject:        [id-cloud] Pending JIRA issues
Sent by:        <id-cloud@lists.oasis-open.org>




Hi Anil, Matt,
 
Looking at the pending items in JIRA that are assigned to me :
 
1.       How do I get an account to log in and update the JIRA pending issues status ?  My OASIS login name and password do not seem to work – should it work  ?  
2.       Specifically, for the items on hand
a.       Item IDCLOUD-13  - per past discussions in the F2F, this should be merged with use case 9 (primekey use case, I believe)
b.      Items IDCLOUD-8 , IDCLOUD-12   is the action item around actor and service normalization ?  the Committee Note Draft (IDCloud-usecases-v1.0-cnd01.doc) seems to be pretty much there already there – could you be kind enough to point me one or two sample issues so I can work them out ?
 
Thanks
Doron
 

The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.




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