| Issue 77: | OAuth supprt in "web" mode. | |
| 7 people starred this issue and may be notified of changes. | Back to list |
[Note: this is for reporting issues on the JaikuEngine open source project. if you are reporting an issue with the jaiku.com service, please send it to support@jaiku.com] What steps will reproduce the problem? 1. Run oauth in a web environment 2. Pass in oauth_callback parameter 3. Nothing happens on authorization of token What is the expected output? What do you see instead? I expect to be redirected to my callback url. Instead of I'm forwarded onto the default authorized.html page. What version of the product are you using? On what operating system? Please provide any additional information below. Attached are two patches. oauth_callback's value was getting lost because of the GET->POST workflow in api_authorize. Moved oauth_callback so that it is captured by the GET request so the Django template could post it back in for the redirect. Passed oauth_token back in the redirect as per the work flow of oauth documentation at oauth.net. The redirect only occured if the token supported web mode. So I had to uncomment the radio buttons in /templates/key.html so that developers could setup keys specifically for the redirecting.
Apr 3, 2009
Also submitted patch at raiku.appspot.com, just in case there is any confusion.
Apr 10, 2009
hey jeff, I don't see your patches at rietku, are you sure they went through?
Apr 14, 2009
No I'm not sure they went through. I tried to upload them again to rietku and it didn't recognize any new changes since my last upload. Can't you just take the diff's from this issue? Sorry for the hassle, but the changes I made were very minor.
Sep 21, 2011
This still seems to be an issue. Any news on when it will be resolved on the jaiku.com site? |
Owner: andyster
Labels: -Priority-Medium Priority-High Size-Small