After a successful FDM token response, which header correctly authenticates a subsequent POST or DELETE to /object/networks?
Select an answer to reveal the explanation.
Short Explanation
The access_token is the badge you clip on for every object call. The refresh token is a later token-hop tool, not something you slap onto /object/networks.
Full Explanation
After the FDM token response, every object POST or DELETE carries Authorization: Bearer with the access_token. Putting the refresh token, the username, or an FDM UI cookie on /object/networks is the wrong constructed header. Refresh is used on a later token request, not as the credential on object calls.