Closed (fixed)
Project:
OpenID Provider
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Sep 2008 at 05:35 UTC
Updated:
30 Mar 2009 at 02:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
sanduhrsIn the previous patch I passed the response, not the request to the hook.
Changed that, now it's possible work with the whole request and decide what to respond.
Patch attached.
Comment #2
sanduhrsAlright, seems we need both ;)
Patch attached.
Comment #3
sanduhrsSwitching order of $request and $response, as in openid.module the first argument is $response, not $request.
Updated patch attached, please have a look.
Comment #4
darren.ferguson commentedPatch looks good to me for the module, it will allow you to check the request for pieces such as attribute exchange and provide the additional information in the response back to the user.
Comment #5
darren.ferguson commentedAfter looking at this, the client side openid module from drupal core implements hook_openid. This is fine since it has the correct variables in it, however i believe for the provider side we need to implement a hook_openid_provider that will deal with the responses. This will allow us to have the hook similar to below:
$op will be response, or signed depending and this way we keep the module away from the client implementation. I think that is a better approach however correct me if i am wrong on this one.
Comment #6
anarcat commentedI agree the hook shouldn't be
hook_openid. Also,hook_openid_provideris a bit too generic, isn't it? Shouldn't we just sayhook_openid_provider_response?Comment #7
asak commentedsubscribing...
Comment #8
anarcat commentedSo this is pretty weird: the code is already there!
So I'm closing this issue, reopen if the feature is still missing.