[Openid-specs-risc] subscription/enrolment - why do we need a receiver API for it?

[Phil Hunt (IDM)]

More importantly, I have not heard a case where users would be allowed to decline security event sharing and still consent to federation. 

The consent we've talked about is part of legal terms in the explicit dialog or of service provider TOS when users supply a foreign recovery email. 

If that is the case I am not sure we need to have a standard api for registration of subscriber subjects. 

Phil

> On Feb 18, 2017, at 12:04 PM, Hardt, Dick <dick at amazon.com> wrote:
> 
> Good question
> 
> When Adam was labeling the implicit and explicit RPs, I originally thought the implicit was the OAuth flow as there was an implicit subscription by the RP of RISC events.
> 
> -- Dick
> 
> On Feb 18, 2017, at 8:55 AM, Phil Hunt <phil.hunt at oracle.com> wrote:
> 
>> A few questions following Thursday’s F2F…
>> 
>> Is there ever a time in RISC where a user who has chosen to federate would not be added to the stream between providers?  And if so, doesn’t the IDP already know this? Why wouldn’t an IDP who is a transmitter just do this automatically?  
>> 
>> Why wouldn’t an IDP just put a subject, who has consented to federation, in the event list for an audience automatically?  
>> 
>> What purpose does it serve to have the receiver call back to register the subject if the receiver has already agreed to an event stream?
>> 
>> Phil
>> 
>> Oracle Corporation, Identity Cloud Services & Identity Standards
>> @independentid
>> www.independentid.com
>> phil.hunt at oracle.com
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Openid-specs-risc mailing list
>> Openid-specs-risc at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-risc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20170218/dfed44e4/attachment.html>