<blockquote>
<p>So what you're saying is that the flow would be that you get a new request token, then when you go to /authorize it would somehow find and return the existing access token rather than creating a new one? The problem with that is that /authorize is implemented by the oauth-plugin gem, not by us.</p>
</blockquote>
<p>No, it should find the last granted token, and if found, use permissions from it for creating a new token. And we already override the <code>oauth1_authorize</code> that processes the request: this is a matter of adding an <code>else</code> block to the <code>if request.post?</code> clause.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/1455#issuecomment-281736003">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLcc1UT4zdhyBhGQl8NOQKbrXaU9Gks5rfGzogaJpZM4MIYe0">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLa1m7y6MF1IGw-_pchJUPThjyIWhks5rfGzogaJpZM4MIYe0.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/openstreetmap/openstreetmap-website/issues/1455#issuecomment-281736003"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Zverik in #1455: \u003e So what you're saying is that the flow would be that you get a new request token, then when you go to /authorize it would somehow find and return the existing access token rather than creating a new one? The problem with that is that /authorize is implemented by the oauth-plugin gem, not by us.\r\n\r\nNo, it should find the last granted token, and if found, use permissions from it for creating a new token. And we already override the `oauth1_authorize` that processes the request: this is a matter of adding an `else` block to the `if request.post?` clause."}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/1455#issuecomment-281736003"}}}</script>