You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Ryan Baxter (JIRA)" <ji...@apache.org> on 2013/10/15 18:52:44 UTC
[jira] [Updated] (SHINDIG-1940) Logging of refresh and access
tokens in BasicOAuth2Request.attemptFetch is misleading
[ https://issues.apache.org/jira/browse/SHINDIG-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Baxter updated SHINDIG-1940:
---------------------------------
Summary: Logging of refresh and access tokens in BasicOAuth2Request.attemptFetch is misleading (was: Logging of refresh and access token in BasicOAuth2Request.attemptFetch is misleading)
> Logging of refresh and access tokens in BasicOAuth2Request.attemptFetch is misleading
> -------------------------------------------------------------------------------------
>
> Key: SHINDIG-1940
> URL: https://issues.apache.org/jira/browse/SHINDIG-1940
> Project: Shindig
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Ryan Baxter
> Assignee: Ryan Baxter
> Fix For: 2.5.1, 2.5.0-update1
>
>
> There is logging at the top of BasicOAuth2Request.attemptFetch to indicate whether the accessor has a refresh and access token. However right now it will log
> BasicOAuth2Request.haveAccessToken(accessor) = true
> BasicOAuth2Request.haveRefreshToken(accessor) = true
> when the accessor does NOT have an access or refresh token.
--
This message was sent by Atlassian JIRA
(v6.1#6144)