You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Brian Eaton (JIRA)" <ji...@apache.org> on 2008/05/27 18:38:03 UTC

[jira] Created: (SHINDIG-310) if service provider revokes token OAuth stops working

if service provider revokes token OAuth stops working
-----------------------------------------------------

                 Key: SHINDIG-310
                 URL: https://issues.apache.org/jira/browse/SHINDIG-310
             Project: Shindig
          Issue Type: Bug
          Components: Gadget Rendering Server (Java)
            Reporter: Brian Eaton


Scenario:
- user installs gadget that uses OAuth
- user approves OAuth access for gadget
- service provider later revokes and/or loses OAuth access token

Expected result: user can reapprove access.

Actual result: OAuth for that user/gadget/service provider combo is broken forever.

I think the solution is to support the OAuth problem reporting extension.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SHINDIG-310) if service provider revokes token OAuth stops working

Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Eaton updated SHINDIG-310:
--------------------------------

    Attachment: oauth-protocol-errors2.patch

Updated after review with balfanz.

> if service provider revokes token OAuth stops working
> -----------------------------------------------------
>
>                 Key: SHINDIG-310
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-310
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadget Rendering Server (Java)
>            Reporter: Brian Eaton
>         Attachments: oauth-protocol-errors2.patch
>
>
> Scenario:
> - user installs gadget that uses OAuth
> - user approves OAuth access for gadget
> - service provider later revokes and/or loses OAuth access token
> Expected result: user can reapprove access.
> Actual result: OAuth for that user/gadget/service provider combo is broken forever.
> I think the solution is to support the OAuth problem reporting extension.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SHINDIG-310) if service provider revokes token OAuth stops working

Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Eaton updated SHINDIG-310:
--------------------------------

    Attachment: oauth-problem-reporting.patch

> if service provider revokes token OAuth stops working
> -----------------------------------------------------
>
>                 Key: SHINDIG-310
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-310
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadget Rendering Server (Java)
>            Reporter: Brian Eaton
>         Attachments: oauth-problem-reporting.patch
>
>
> Scenario:
> - user installs gadget that uses OAuth
> - user approves OAuth access for gadget
> - service provider later revokes and/or loses OAuth access token
> Expected result: user can reapprove access.
> Actual result: OAuth for that user/gadget/service provider combo is broken forever.
> I think the solution is to support the OAuth problem reporting extension.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SHINDIG-310) if service provider revokes token OAuth stops working

Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Eaton updated SHINDIG-310:
--------------------------------

    Attachment:     (was: oauth-problem-reporting.patch)

> if service provider revokes token OAuth stops working
> -----------------------------------------------------
>
>                 Key: SHINDIG-310
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-310
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadget Rendering Server (Java)
>            Reporter: Brian Eaton
>         Attachments: oauth-protocol-errors2.patch
>
>
> Scenario:
> - user installs gadget that uses OAuth
> - user approves OAuth access for gadget
> - service provider later revokes and/or loses OAuth access token
> Expected result: user can reapprove access.
> Actual result: OAuth for that user/gadget/service provider combo is broken forever.
> I think the solution is to support the OAuth problem reporting extension.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SHINDIG-310) if service provider revokes token OAuth stops working

Posted by "Brian Eaton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Eaton resolved SHINDIG-310.
---------------------------------

    Resolution: Fixed

Fixed in shindig 664213.

> if service provider revokes token OAuth stops working
> -----------------------------------------------------
>
>                 Key: SHINDIG-310
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-310
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadget Rendering Server (Java)
>            Reporter: Brian Eaton
>         Attachments: oauth-protocol-errors2.patch
>
>
> Scenario:
> - user installs gadget that uses OAuth
> - user approves OAuth access for gadget
> - service provider later revokes and/or loses OAuth access token
> Expected result: user can reapprove access.
> Actual result: OAuth for that user/gadget/service provider combo is broken forever.
> I think the solution is to support the OAuth problem reporting extension.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.