[Openid-specs-ab] Request artifact

Nat sakimura at gmail.com
Wed Apr 28 14:32:33 UTC 2010


John,

I am open to call request artifact as something else, but I do not  
think it is a good idea to combine the request artifact and rpfurl as  
the randomness requirement is very different.

=nat @ Tokyo via iPhone

On 2010/04/28, at 23:25, John Bradley <jbradley at mac.com> wrote:

> Nat,
>
> One simplification to consider for 7.6 may be to combine artifact  
> and rpfurl.
>
> If the OP has returned artifact that could be:
> Some internal refrence ID.
> A URL pointing to some internal reference.
> Some compressed version of the request.
>
> If we think of the value as a reference to the request then the  
> rpfurl is also a reference to the request.
>
> The only difference is that one is defined by the OP and the other  
> by the RP.
>
> It may be confusing for people to have two things called artifact  
> one for the request and one for the response.
>
> The request could be renamed to something like request_refrence
>
> Some people may prefer them separate to make validation easier.
>
> It is not a big thing.
>
> John B.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20100428/769d1f8a/attachment.htm>


More information about the Openid-specs-ab mailing list