Closed (won't fix)
Project:
Simple OAuth (OAuth2) & OpenID Connect
Version:
5.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Apr 2019 at 07:45 UTC
Updated:
19 Jan 2026 at 15:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
br0kenPoC
Comment #3
br0ken@e0ipso, what is the best way to locate a corresponding refresh token by an access token?
Comment #4
br0kenComment #5
e0ipsoI can't remember at the moment. I kind of think that we've had issues around this in the past.
Comment #6
e0ipsoThis patch:
hook_entity_insert.This makes it a good candidate for a separate contrib. @BR0kEN have you considered that approach? I'll be happy to link to it in the project page.
Comment #7
br0kenI was thinking about a submodule (kinda `simple_oauth_tokens_limit`) but came up that simply having a default configuration that disables the feature is enough since it does not introduce any breaking changes.
So, by default `simple_oauth` behaves as it was before. Then, only when someone changes the configuration, it starts limiting access tokens.
@e0ipso, are you against implementing this in `simple_oauth` or should I propose another approach?
Comment #8
e0ipso@BR0kEN I think this is a very valid feature. However, as you well know, this module already has MANY features to maintain. I am quite choosy on what gets in. One key factor I consider is does this benefit the majority of the installs? In this case I think the feature is very useful, but not everyone will need it. That's why I'm reticent to have to maintain it (as an optional feature).
Comment #9
bradjones1Agreed that this might be useful to some but probably belongs in a separate contrib module in this ecosystem. Marking as active and bumping versions.
Comment #10
ssob_ii commentedHow can I add this file into my code?
Comment #11
bojan_dev commentedClosing this issue because we do not plan to support this feature in simple_oauth.