Associate token to custom account

[CyndyMo]

I'm probably missing something obvious, but since I can choose to mint to a custom account, as defined in the VC, I would like to be able to associate the token to that account within the policy such that the mint and transfer will be successful. However, when I choose the token action block the only option I have for Associate is "Default". Is there a way to make the association to a custom account within the policy, prior to the mint event, that I am missing?

[anvabr]

Hi @CyndyMo, there is an example of this in the Remote Work GHG policy. In this policy the target user Hedera account is inputted into a VC at the org registration stage, and then the token is associated with this account ( account private key is required for this). In summary, to add token association to an account you'd need:

• use tokenConfirmationBlock.
• use Custom option for the account.
• input the name of the account field from the VC into the Account Id field.

[CyndyMo]

Hi @anvabr I'm just getting back to this and have some questions. I've attached a policy in which I've tried to add the token confirmation block and I feel like:

1. I may not have the block in the correct sequence in the workflow because...
2. The block is not recognizing the account ID I've entered in the claim document (field wallet_id)

My second (third?) question is, if the account private key was held in secrets mgr, is there a way I can use the apis to feed the key to the token confirmation block, or is it always going to request the data as what looks like a string field in the UI?

policy_1712154666045.zip

[anvabr]

Hi @CyndyMo , our developers have done some edits on your policy, please see the attached policy with their corrections:

• missing event type for the tokenConfirmationBlock (it should be confirm)
• errors in the trustchain filters
• one of the filters missing
• corrected key input so it works in situations where multiple documents appear simultaniously

All other logic is left intact. Hopefully this answers your questions.
B4E_IWA_REC_5.policy.zip

[CyndyMo]

Thank you @anvabr I'm sure it is much better. The last thing I was asking about was secret manager integration. Do you know if this is possible or will it always expect the key?

[anvabr]

Sorry, missed that one. Probably because unfortunately at the moment there is no such functionality, i.e. you are right in thinking it will always accepts the string with the key when POST request of SET BLOCK DATA is sent, by tag or uuid.