Introduction
In this article, we will discuss how to resolve the “Failed to parse token” error when migrating to RTFS from legacy federation.
This error occurs when an Identity Token or Reference Token is used while performing the command to execute the migration to the standalone Federation service:
jf federation-migrator migrate_rt <base url without /artifactory> <token>
In the logs from the migration CLI tool, we will see entries similar to the ones below:
[main] WARN o.j.r.logic.network.HttpClientImpl - Request failed with status 500, response: {"status":500,"message":"Failed to parse token.","traceId":"<TRACE_ID>"}
[main] WARN o.j.r.logic.network.HttpClientImpl - Request failed with status 500, response: {"status":500,"message":"Failed to parse token.","traceId":"<TRACE_ID>"}
[main] WARN o.j.r.logic.network.HttpClientImpl - Request failed with status 500, response: {"status":500,"message":"Failed to parse token.","traceId":"<TRACE_ID>"}
[main] WARN o.j.r.logic.network.HttpClientImpl - Request failed with status 500, response: {"status":500,"message":"Failed to parse token.","traceId":"<TRACE_ID>"}
[main] WARN o.j.r.logic.network.HttpClientImpl - Request failed with status 500, response: {"status":500,"message":"Failed to parse token.","traceId":"<TRACE_ID>"}
[main] ERROR o.j.r.logic.network.HttpClientImpl - Request failed after 5 attempts. Last error: Expected status 200 however received status: 500
2026-05-11 16:53:34 [main] ERROR o.j.r.l.migration.RtToRtfsMigration - Failed to import RTFS config batch
org.jfrog.rtfs.exceptions.network.RtfsBridgeException: Request failed after multiple retry attempts
By taking the TRACE_ID from the migration tool error logs above, we can see the relevant logs in artrifactory-federatation-service.log:
[jfrtfs] [WARN ] [<TRACE_ID>] [ ] [.r.r.GlobalExceptionHandler:96] [http-nio-8025-exec-9] - Caught an error - Failed to parse token.java.lang.IllegalArgumentException: Failed to parse token.
...
...
Caused by: java.text.ParseException: Invalid serialized unsecured/JWS/JWE object: Missing part delimiters
at com.nimbusds.jose.JOSEObject.split(JOSEObject.java:226)
at com.nimbusds.jwt.SignedJWT.parse(SignedJWT.java:129)
at org.jfrog.access.token.JwtAccessTokenImpl.parseTokenValue(JwtAccessTokenImpl.java:58)
The "Failed to parse token" and "Missing part delimiters" errors are caused by using a non-JWT Token where a JWT Access Token is required.
Generating a scoped Access Token directly from the Administration User Management settings will resolve the formatting mismatch and allow your RTFS migration to complete successfully.
Resolution
To resolve this error, it is required to replace the Token with a scoped Access Token.
Below you can find the steps to resolve this error:
- Log in to Artifactory as an admin user.
- Navigate to: Administration Tab -> User Management -> Access Tokens -> Generate Token.
For example:
3. Re-execute the command to complete the RTFS migration.
jf federation-migrator migrate_rtfs ‹base url without
/artifactory> <scoped token>