You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Matthias Niederhausen (JIRA)" <ji...@apache.org> on 2012/10/08 11:06:03 UTC
[jira] [Created] (WOOKIE-385) Improve integration of oAuth
authorization into workflow
Matthias Niederhausen created WOOKIE-385:
--------------------------------------------
Summary: Improve integration of oAuth authorization into workflow
Key: WOOKIE-385
URL: https://issues.apache.org/jira/browse/WOOKIE-385
Project: Wookie
Issue Type: Improvement
Components: Feature Management
Affects Versions: 0.14.0
Reporter: Matthias Niederhausen
Priority: Minor
The oAuth authorization step could be better integrated into widgets' workflows. Two different actions could be taken:
1. Allow to show the authorization page in an iframe. The iframe could be shown as an overlay within the widget and not as a popup (which disrupts and also has usability issues on mobile devices).
2. Offer developers some callback function when calling oAuth.authenticate() that is called when the process has completed. For my widget, I am currently using the construct:
oAuth.authenticate();
var timer = setInterval(function() {
if (oAuth.status == "F") {
alert("Could not load contacts.");
clearInterval(timer);
}
else if (oAuth.status == "A") {
loadGoogleContacts();
clearInterval(timer);
}
}, 500);
Usually, one wants to load data immediately after access has been granted (or denied). I guess that other developers will want something similar, so maybe integrate it into the oAuth library?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-385) Improve integration of oAuth
authorization into workflow
Posted by "Matthias Niederhausen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493078#comment-13493078 ]
Matthias Niederhausen commented on WOOKIE-385:
----------------------------------------------
Duh, damnit =)
Just found a bug in my test code. So, false alert. Everything is working okay with the current version. You can mark this as fixed.
> Improve integration of oAuth authorization into workflow
> --------------------------------------------------------
>
> Key: WOOKIE-385
> URL: https://issues.apache.org/jira/browse/WOOKIE-385
> Project: Wookie
> Issue Type: Improvement
> Components: Feature Management
> Reporter: Matthias Niederhausen
> Priority: Minor
> Fix For: 0.13.0
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> The oAuth authorization step could be better integrated into widgets' workflows. Two different actions could be taken:
> 1. Allow to show the authorization page in an iframe. The iframe could be shown as an overlay within the widget and not as a popup (which disrupts and also has usability issues on mobile devices).
> 2. Offer developers some callback function when calling oAuth.authenticate() that is called when the process has completed. For my widget, I am currently using the construct:
> oAuth.authenticate();
>
> var timer = setInterval(function() {
> if (oAuth.status == "F") {
> alert("Could not load contacts.");
> clearInterval(timer);
> }
> else if (oAuth.status == "A") {
> loadGoogleContacts();
> clearInterval(timer);
> }
> }, 500);
> Usually, one wants to load data immediately after access has been granted (or denied). I guess that other developers will want something similar, so maybe integrate it into the oAuth library?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-385) Improve integration of oAuth
authorization into workflow
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497452#comment-13497452 ]
Scott Wilson commented on WOOKIE-385:
-------------------------------------
Thanks Matthias :)
> Improve integration of oAuth authorization into workflow
> --------------------------------------------------------
>
> Key: WOOKIE-385
> URL: https://issues.apache.org/jira/browse/WOOKIE-385
> Project: Wookie
> Issue Type: Improvement
> Components: Feature Management
> Reporter: Matthias Niederhausen
> Priority: Minor
> Fix For: 0.13.0
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> The oAuth authorization step could be better integrated into widgets' workflows. Two different actions could be taken:
> 1. Allow to show the authorization page in an iframe. The iframe could be shown as an overlay within the widget and not as a popup (which disrupts and also has usability issues on mobile devices).
> 2. Offer developers some callback function when calling oAuth.authenticate() that is called when the process has completed. For my widget, I am currently using the construct:
> oAuth.authenticate();
>
> var timer = setInterval(function() {
> if (oAuth.status == "F") {
> alert("Could not load contacts.");
> clearInterval(timer);
> }
> else if (oAuth.status == "A") {
> loadGoogleContacts();
> clearInterval(timer);
> }
> }, 500);
> Usually, one wants to load data immediately after access has been granted (or denied). I guess that other developers will want something similar, so maybe integrate it into the oAuth library?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-385) Improve integration of oAuth
authorization into workflow
Posted by "Hoang Minh Tien (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471478#comment-13471478 ]
Hoang Minh Tien commented on WOOKIE-385:
----------------------------------------
Good point, thanks Matthias, I've update, when calling authenticate you pass a callback function as parameter
e.g.:
oauth.authenticate(function(result) {
// result['error'] : 'success' or other oauth error code
// result['desc'] : string which describe error
// you can implement custom implementation here
});
> Improve integration of oAuth authorization into workflow
> --------------------------------------------------------
>
> Key: WOOKIE-385
> URL: https://issues.apache.org/jira/browse/WOOKIE-385
> Project: Wookie
> Issue Type: Improvement
> Components: Feature Management
> Affects Versions: 0.14.0
> Reporter: Matthias Niederhausen
> Priority: Minor
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> The oAuth authorization step could be better integrated into widgets' workflows. Two different actions could be taken:
> 1. Allow to show the authorization page in an iframe. The iframe could be shown as an overlay within the widget and not as a popup (which disrupts and also has usability issues on mobile devices).
> 2. Offer developers some callback function when calling oAuth.authenticate() that is called when the process has completed. For my widget, I am currently using the construct:
> oAuth.authenticate();
>
> var timer = setInterval(function() {
> if (oAuth.status == "F") {
> alert("Could not load contacts.");
> clearInterval(timer);
> }
> else if (oAuth.status == "A") {
> loadGoogleContacts();
> clearInterval(timer);
> }
> }, 500);
> Usually, one wants to load data immediately after access has been granted (or denied). I guess that other developers will want something similar, so maybe integrate it into the oAuth library?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WOOKIE-385) Improve integration of oAuth
authorization into workflow
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson updated WOOKIE-385:
--------------------------------
Affects Version/s: (was: 0.14.0)
Fix Version/s: 0.13.0
Marking as fixed in 0.13
> Improve integration of oAuth authorization into workflow
> --------------------------------------------------------
>
> Key: WOOKIE-385
> URL: https://issues.apache.org/jira/browse/WOOKIE-385
> Project: Wookie
> Issue Type: Improvement
> Components: Feature Management
> Reporter: Matthias Niederhausen
> Priority: Minor
> Fix For: 0.13.0
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> The oAuth authorization step could be better integrated into widgets' workflows. Two different actions could be taken:
> 1. Allow to show the authorization page in an iframe. The iframe could be shown as an overlay within the widget and not as a popup (which disrupts and also has usability issues on mobile devices).
> 2. Offer developers some callback function when calling oAuth.authenticate() that is called when the process has completed. For my widget, I am currently using the construct:
> oAuth.authenticate();
>
> var timer = setInterval(function() {
> if (oAuth.status == "F") {
> alert("Could not load contacts.");
> clearInterval(timer);
> }
> else if (oAuth.status == "A") {
> loadGoogleContacts();
> clearInterval(timer);
> }
> }, 500);
> Usually, one wants to load data immediately after access has been granted (or denied). I guess that other developers will want something similar, so maybe integrate it into the oAuth library?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira