On 22-Oct-07, at 3:23 AM, James Henstridge wrote:
>> If the RP does not store any user attributes (and requests them with
>> each transaction from the OP), why does it want to be updated when
>> the user changes an attribute value at their OP?
>
> What I meant was that the RP would act as a cache
On 18/10/2007, Johnny Bufu <[EMAIL PROTECTED]> wrote:
> Hi James,
>
> On 17-Oct-07, at 2:42 AM, James Henstridge wrote:
>
> > I have a few more questions about the update_url feature of OpenID
> > attribute exchange that I feel could do with answers in the
> > specification.
> >
> > For the questio
On 17-Oct-07, at 2:42 AM, James Henstridge wrote:
> The next one is not so much a question as an observation: As an
> identity URL may change its delegation over time (possibly without the
> underlying OP's knowledge), it is possible that an RP will receive
> updates from an OP that is not author
On 17-Oct-07, at 2:42 AM, James Henstridge wrote:
> The next question is how much information from the original OpenID
> authentication request/response can the RP expect to be included in
> the subsequent update responses.
Attribute Exchange is an OpenID extension, so a full/valid/positive
as
Hi James,
On 17-Oct-07, at 2:42 AM, James Henstridge wrote:
> I have a few more questions about the update_url feature of OpenID
> attribute exchange that I feel could do with answers in the
> specification.
>
> For the questions, imagine an OpenID RP with the following properties:
>
> 1. The RP
I have a few more questions about the update_url feature of OpenID
attribute exchange that I feel could do with answers in the
specification.
For the questions, imagine an OpenID RP with the following properties:
1. The RP provides a unified login/signup workflow, so that if a user
signs in with
