"Refreshed the access token expiry" is confusing.

[glensc]

First I thought the message was fetching refresh token for the plex token, and that got me thinking, where does it store the refresh token, in memory? didn't see anything in the disk.

But looking at the source, it just sends a test request (aka ping) and does nothing with the result?:

• watchlistarr/src/main/scala/plex/PlexUtils.scala

  Lines 36 to 50 in 9b31fad

  	protected def ping(client: HttpClient)(config: PlexConfiguration): IO[Unit] = {
  	config.plexTokens.map { token =>
  	val url = Uri
  	.unsafeFromString("https://plex.tv/api/v2/ping")
  	.withQueryParam("X-Plex-Token", token)
  	.withQueryParam("X-Plex-Client-Identifier", "watchlistarr")
  	client.httpRequest(Method.GET, url).map {
  	case Right(_) =>
  	logger.info(s"Refreshed the access token expiry")
  	case Left(err) =>
  	logger.warn(s"Unable to ping plex.tv: $err")
  	}
  	}
  	}.toList.sequence.map(_ => ())

[nylonee]

Ah yeah, this confused me as well, it turns out that Plex handles 'token refresh' in a different way

It looks like when the token is validated on the Plex size, it's also "renewed" in their backend. If the token were a JWT, it would have a claims set that would have a fixed expiry date, but because it's not a JWT, I guess Plex just decides they can do whatever they want with their token.

Pinging the Plex token regularly ensures that it does not get invalidated on the Plex backend.

We only have empirical evidence to support this - I've been running the same token on my server for 6 months and it hasn't expired, so that's a big step up from the previous expiry times (1-2 months on Overseer)

[glensc]

maybe change "Refreshed the access token expiry" to "Pinged Plex API Server to update access token expiry"

but closing, as it's not a "wrong" message.