OkHttp 身份验证器在成功刷新令牌请求后循环

Question

>我已经实现了类扩展okhttp3.Authenticator以及Retrofit 2，用于处理我的Android应用程序中的401错误。它应该调用 refreshToken 请求，如果成功，则使用新的访问令牌调用所需的请求。问题是成功获得刷新令牌后，我的TokenAuthenticator... 一次又一次地刷新令牌，直到达到某个限制。你知道发生了什么吗？

令牌身份验证器类：

class TokenAuthenticator : Authenticator {
private val notLoggedResponseCode = 401
private val successResponseCode = 200
private val refreshTokenGrantType = "refresh_token"
override fun authenticate(route: Route?, response: okhttp3.Response?): Request? {
if (response?.code() == notLoggedResponseCode) {
val refreshTokenResponse: Response<Authorization> = RestController
.getInstance()
.basicRetrofit
.create(AuthRepository::class.java)
.refreshToken(
Credentials.basic(BuildConfig.CLIENT_ID, BuildConfig.CLIENT_SECRET),
refreshTokenGrantType,
UserSession.getInstance().authorization?.refreshToken!!)
.execute()

return if (refreshTokenResponse.code() == successResponseCode) {
UserSession.getInstance().authorization = refreshTokenResponse.body() //updating token
UserSession.getInstance().saveAuthorizationData()
// Every time flow is here, so new access token is obtained.
// But somehow it starts refresh procedure again... 
response
.request()
.newBuilder()
.build()
} else {
null
}
} else {
return null
}
}
}

初始化 OkHttp 客户端以进行改造的方法：

private fun initBaseOkHttpClientBuilder(): OkHttpClient.Builder {
val logging = HttpLoggingInterceptor().apply {
this.level = HttpLoggingInterceptor.Level.BODY
}
return OkHttpClient.Builder()
.connectTimeout(connectionTimeout, TimeUnit.SECONDS)
.readTimeout(connectionTimeout, TimeUnit.SECONDS)
.writeTimeout(connectionTimeout, TimeUnit.SECONDS)
.addInterceptor(logging)
.authenticator(TokenAuthenticator())
.addInterceptor(OAuth2Interceptor())
}

Answer 1

获取刷新令牌时，需要将其传递给标头中的新请求。 类似response.request().newBuilder().header("Authorization", "bearer " + bearer).build()