Source evidence

Remove refresh token

WP OAuth Server (OAuth Authentication) · support · 2024-01-20T20:25:00+00:00

WP OAuth Server (OAuth Authentication) plugin evidence original source source API

complaintsentiment

mediumseverity

0.69relevance

0replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

2 / 18 rows with source links

11.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

16 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

johannschnagl unresolved

I just tried and deleted a test user from my wordpress site. The user was logged in and continued to use his refresh token to get new access tokens. What is the best way to handle this? I expected you code to check if the user exists on a token refresh I assume I could use the wo_before_token_method hook and just die if the user doesn’t exist any more I assume I could just delete the user’s refresh tokens from the database when the user is deleted.

Commercial Context

Opportunity

access control and account operations

Oauth access-control assurance for keeping user access, permissions, and protected content correct

Buyer: membership site owners, agencies, and operations teams

Wedge: test oauth roles, protected content, SSO/login handoffs, and private-data exposure

Investigate Pain card complete market

Analysis

heuristic-v1

Summary: Remove refresh token: users show performance pain that may indicate a product gap.

Evidence quote: What is the best way to handle this?

Affected feature: performance

performance quality

Plugin

API

WP OAuth Server (OAuth Authentication)

3.0K active installs · 178.8K downloads · rating 76.0

oauth oauth provider oauth2 oauth2 service provider

Comments

0 shown

No comments were stored for this source.