[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Use Case & Requirements Doc Strawman 1 Issues List
> ISSUE[UC-1-02:ThirdParty] Use case scenario 3 (single sign-on, third > party) describes a scenario in which a Web user logs in to a > particular 3rd-party security provider which returns an authentication > reference that can be used to access multiple destination Web > sites. Is this different than Use case scenario 1 (single sign-on, > pull model)? If not, should it be removed from the use case and > requirements document? This is clearly a case of redundancy. If it is a third-party security provider or business party ought to be technology-independent IMO.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC