[OpenID] CheckIDRequest with Big AX

[larry drebes]

The use case is legit.   The OpenID flow is through the user agent, the user
is redirected to the OP, the OP redirects back to the RP.  For backchannel
access to data (where access has previously been granted), oauth or a
callback url are much simpler flows than than going through the user agent
redirect.    larry-

On Tue, Dec 30, 2008 at 5:25 AM, Pat Cappelaere <pat at cappelaere.com> wrote:

> I think that AX is used in its designed role here.The user grants access
> to his information.
> The SP ought to be free to access that information at anytime and
> update/store stuff at anytime, right?
> This seems reasonable to me and very appropriate to leverage that
> capability at the enterprise level.
> Pat.
>
>
> On Dec 30, 2008, at 6:59 AM, Peter Williams wrote:
>
> This begs a wider question concerning AX. The underlying issue relates to
> my own confusion over the wider role of AX (expressed in a thread a week or
> two ago).
>
> For Dick, evidently AX is the extensible form of sreg – and is about a
> visible user-centric experience (e.g. a signup wizard). It's little more.
> There is a bit of stuff about AX update.
>
> For others, two websites may be exploiting an _*existing*_ openid pairwise
> security association to signal each other over that authenticated channel,
> using AX extensions for requests/response FOR PER-APPLICATION PURPOSES. This
> may be occurring OUTSIDE a visible user experience (such as signup form
> population). The user may have no interactive role. One might only set a
> config policy of "please sync me every 10m", and 10 AX transactions occur
> over 10 hidden iframes (every 10m).
>
> Im with Pat on AX; doing the kind of thing he is doing is what it seemed to
> be saying it was for...
>
> As with XRI, the power of openid is its architecture and the enabling that
> XRI/XDI/AX/URls provide to app developers. It's not the particular GUI
> practice today – which at the end of the day is just another websso protocol
> that also ran. Since any and all websso is however a fundamental enabler
> (because it brings with it solutions to security associations, consent, and
> impersonated session management), its what now follows from and develops on
> the openid architecture that is the _*really*_ interesting stuff.
>
>
>
>
> *From:* general-bounces at openid.net [mailto:general-bounces at openid.net<general-bounces at openid.net>
> ] *On Behalf Of *larry drebes
> *Sent:* Tuesday, December 30, 2008 3:19 AM
> *To:* Pat Cappelaere
> *Cc:* general at openid.net List
> *Subject:* Re: [OpenID] CheckIDRequest with Big AX
>
> Hi Pat,
> The normal behavior for an OP is to assume the user is in the loop.  With
> javascript enabled the form POST submit should happen automatically, for the
> vast majority of time this is not pestering the user.
> larry-
> On Mon, Dec 29, 2008 at 7:46 PM, Pat Cappelaere <pat at cappelaere.com>
> wrote:
> I have an interesting problem.
>
> I am trying to make a CheckIDRequest along with a few experimental AX.
> Problem is that my attributes are fairly large and could overflow the
> GET.
> The Janrain Ruby library detects that and turns the response into a
> secondary form.  A user has to hit continue for the form to do a
> post.  This is fine if there is a user in the loop (although confusing
> at best) but this is not my case.  I do not have a user in the loop.
> I am really trying to authenticate an application consumer that
> happens to have an openid and trying to get its pubic key in order to
> do the OAuth dance using AX... cool stuff...
>
> My questions are:
>
> Is this the normal behavior of an OP?
>
> Should I try to patch the server library to return a directPOST?
>
> Or get my consumer to break down the request in two parts?  I am not
> quite sure how the second part would look like though...
>
> Any suggestions?
>
> Thanks,
>
> Pat.
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>
>
>
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20081230/f82422e4/attachment-0002.htm>