<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [PROPOSAL] bare response / bare request</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I'm confused, can you explain this again please?<BR>
<BR>
--David<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: specs-bounces@openid.net on behalf of Dick Hardt<BR>
Sent: Sat 9/30/2006 5:09 PM<BR>
To: specs@openid.net<BR>
Subject: [PROPOSAL] bare response / bare request<BR>
<BR>
Motivating Use Case<BR>
----------------------------<BR>
The IdP would like to allow the user to click a link on the IdP to <BR>
login to an RP. This requires a bare response to be able to be sent.<BR>
A Trusted Party, acting as an RP would like to store a value at the <BR>
IdP, but does not need the IdP to send the user back, a bare request <BR>
is needed.<BR>
<BR>
<BR>
Proposed Implementation<BR>
-----------------------------------<BR>
bare request: if the openid.return_to parameter is missing or blank, <BR>
then the IdP will not send the user back to the RP<BR>
<BR>
bare response: sending a bare response is valid (not sure we need to <BR>
do anything more then say it is OK to do)<BR>
_______________________________________________<BR>
specs mailing list<BR>
specs@openid.net<BR>
<A HREF="http://openid.net/mailman/listinfo/specs">http://openid.net/mailman/listinfo/specs</A><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>