[OpenID] [oauth] Re: Replacing email verification with RSS 'push' feeds and OAuth

John Panzer jpanzer at acm.org
Tue Apr 7 18:17:39 UTC 2009


A temporary email address is probably more immediately deployable.  However,
if there's interest, providing a POST endpoint to send something like an
Atom Entry to, guarded by OAuth via the Authorization: header, is pretty
well understood standards-based technology with libraries already written.
It could also be used for "out of band" communications to an end user as
well.

The Achilles Heel of email based communication of all kinds is spam
filtering -- if the temporary email address just forwards, and nothing else
special is done, I would guess that a lot of the emails sent will end up in
a spam folder.

On Tue, Apr 7, 2009 at 7:00 AM, Paul Madsen <paul.madsen at gmail.com> wrote:

>  because the RP would still have a whitelist .....
>
> I see Allen's example as a specific case of 'for a given trusted OP, I am
> more willing to trust attribute X than Y'. In his case its because the
> asserted email address matched the OP's domain ....
>
> But the RP still has to start with 'trusting' the OP, through a whitelist
> or something more flexible.
>
> paul
>
>
> Andrew Arnott wrote:
>
> Allen,
>  It sounds like you're proposing that an RP trust the email claim from an
> OP if the domain of the OP and the domain of the email match.  Is that
> right?  If so, what's to stop me from setting my myrogueOP.com, and
> asserting an email claim for myinvalidemail at myrogueOP.com and getting into
> web sites without a valid email address?
> --
> Andrew Arnott
> "I [may] not agree with what you have to say, but I'll defend to the death
> your right to say it." - Voltaire
>
>
> On Mon, Apr 6, 2009 at 9:34 PM, Allen Tom <atom at yahoo-inc.com> wrote:
>
>> Currently, Google OpenID users can be exempted from Email verification
>> when the Google OP returns an @gmail.com address, because the Google OP
>> will only return the @gmail.com address that is tied to the Google
>> Account.
>>
>> If we generalize this, if the RP trusts the user's email provider to
>> always assert the user's true email address, then why wouldn't an RP trust
>> the OP to always return a valid disposable email address?
>>
>> Allen
>>
>>
>> Andrew Arnott wrote:
>>
>> True. This is a model I thought of a while back, when some credit cards
>> started generating one-time-use credit card numbers for use when shopping
>> online.  I think this has a much higher chance of working for people,
>> although it doesn't at all solve the problem of RP's needing to send the
>> user through email verification.
>> --
>> Andrew Arnott
>> "I [may] not agree with what you have to say, but I'll defend to the death
>> your right to say it." - Voltaire
>>
>>
>> On Mon, Apr 6, 2009 at 8:42 PM, Allen Tom <atom at yahoo-inc.com> wrote:
>>
>>>
>>> Andrew Arnott wrote:
>>> >
>>> > Thanks.  Incidentally, the grief I have with Facebook is that I have
>>> > to visit Facebook in order to pick up my "mail" which may just be a
>>> > poke or prod.  *grumble*  But yes, I'd like to see us provide a
>>> > general solution.  And my personal queuing SP of choice would likely
>>> > be one that sends copies of my messages in the email it sends me, as
>>> > well as organizes them within its own web site for my review later.
>>> >
>>>
>>>  What if the OP generated a unique disposable email address for each RP
>>> that the user wants to allow email, and the OP just forwards it on to
>>> the user's real mailbox (or cell phone or IM, depending on the user's
>>> preference). If and when the user no longer wants to receive messages
>>> from the RP, the user can just deactivate the disposable email address.
>>>
>>> This might be easier to deploy than defining a standard messaging API
>>> and putting OAuth in front of it.
>>>
>>> Allen
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>
> --
> Paul Madsen            e:paul.madsen @ gmail.com
>                        m:613-282-8647
>                        web:connectid.blogspot.com
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "OAuth" group.
> To post to this group, send email to oauth at googlegroups.com
> To unsubscribe from this group, send email to
> oauth+unsubscribe at googlegroups.com <oauth%2Bunsubscribe at googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/oauth?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20090407/9025dba3/attachment.htm>


More information about the general mailing list