oauth: web application reauthorization creates table spam

ExportXMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Normal
    • 2013-03-25
    • Affects Version/s: None
    • Component/s: None
    • None

      Though now it doesn't ask for you to click the "Allow" button every time (yay! thanks MBS-5946 ), we still get a new token and a new table entry every time someone re-logs-in in geordi. I'm not sure about the appropriate security implications, but I guess that either a new token shouldn't be created (and the old one returned), or the old token(s) of the same scope and application should be deleted when a new one is created.

            Assignee:
            Lukáš Lalinský
            Reporter:
            Ian McEwen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2013-03-25