[
https://issues.apache.org/jira/browse/CXF-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730764#comment-13730764
]
Sergey Beryozkin commented on CXF-5180:
---------------------------------------
Sure, you are right, AT already has a link.
Would supporting a two-way relationship can make any difference as far as the
speed of look-ups is concerned,
If we have a really large number of ATs then going to them from RT would be an
alternative ?
In other words, would that negatively affect your current implementation (as
far as the DB mappings are concerned) if I do add List of String to
RefreshToken (which you would not have to fill in if not needed in your case) ?
> Adding RefreshToken as token type
> ---------------------------------
>
> Key: CXF-5180
> URL: https://issues.apache.org/jira/browse/CXF-5180
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS Security
> Affects Versions: 2.7.6
> Reporter: Thorsten Hoeger
> Priority: Minor
> Labels: OAuth2
> Attachments: 0001-adding-RefreshToken-type.patch
>
>
> It may be useful to have a dedicated RefreshToken class (subclassing
> ServerAccessToken) to represent the generated refresh token. This allows
> implementors to drop the BearerAccessToken on expiry and persist the
> RefreshToken until used by the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
