Claims do not authorize to act as party

Questions
1

Hello, I am trying to mint via the API request but got this error msg.
However, via the utility UI, I can mint using the same PartyId with no problem. This issue occurred after the upgrade my validator in Devnet to 0.5.1.

{"@timestamp":"2025-11-19T14:33:48.790Z","message":"Request com.daml.ledger.api.v2.CommandService/SubmitAndWaitForTransaction by inprocess-grpc-5001: received a message \n  Request tid:9800ba569988ecd802137faba00a7468","logger_name":"c.d.c.n.g.ApiRequestLogger:participant=participant","thread_name":"canton-env-ec-209","level":"DEBUG","span-id":"ba83558475e58324","span-parent-id":"ed837983710e1149","trace-id":"9800ba569988ecd802137faba00a7468","span-name":"logger"}
{"@timestamp":"2025-11-19T14:33:48.791Z","message":"PERMISSION_DENIED(7,9800ba56): Claims do not authorize to act as party 'auth0_007c68ff6359e461eb44340b9312::1220ebc214b871e5c96a4a5e060ca8c9573a4d39ad705feb11523345c0e7d29b1a3d'","logger_name":"c.d.c.a.Authorizer:participant=participant","thread_name":"canton-env-ec-209","level":"WARN","trace-id":"9800ba569988ecd802137faba00a7468","location":"Authorizer.scala:148","span-id":"ed837983710e1149","error-code":"PERMISSION_DENIED(7,9800ba56)","span-parent-id":"045116b096a7e210","participant":"participant","span-name":"com.daml.ledger.api.v2.CommandService/SubmitAndWaitForTransaction"}
2

Background: In the Utilities UI, you are logged in as a User. The User has a primary party. When you take actions in the Utilities UI, it is that primary party that the Utilities UI is using. When you send an API request, you are sending a token with a sub field with the name of a User.

Suggestions:

  1. Compare the token’s sub field (which you are passing to the Ledger API) with the User used to log into the Utilities UI. Are they the same value?

  2. Also, try grabbing the token from Utilities UI’s browser developer window. Does that token work when hitting the Ledger API? If so, what is different between the two tokens?

2 Likes