eclipse-ee4j / eclipse-ee4j/jersey

Please consider making OAuth2ClientFeature a public class

Open
#3,429 3 comments 1 reaction 0 assignees View on GitHub
Component: extensions Priority: Minor Type: Improvement
Dominant language
Java
Stars
730
Forks
382
PR merge metrics
No merged PRs in 30d

Description

We have a use case where there is an OAuth2 request back end to back end, with no user interaction possible, so that it appears OAuth2CodeGrantFlow is not a possible solution as this flow expects user interaction, The user has already generated an Access Token and Refresh Token using OAuth2CodeGrantFlow that is stored in a database.

We wish to use the OAuth2ClientFeature as follows
Feature feature = new OAuth2ClientFeature();
client.register(feature);

However this is not possible as the class is package private. Also this would not handle the case that the AccessToken has expired.

Please confirm if this is a valid use case, or is there another way to accomplish what we want.
#### Affected Versions
[2.23.2]

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.