I am developing a project using DAML Hub with sample marketplace app.
When allocationg a new party with following link (json api + service account access token).
I have a problem and I want to get help.
Party allocation via DAML Hub console URL is fine. However, it seems to be private or unavailable from my external website.
Moreover, only in DAML Hub, party allocation via json API response with this error message.
“party allocation unsupported for now”
It is working in local DAML ledger.
https://{ledgerId}.daml.app/v1/parties/allocate
Then, my question is
Is party allocation in Hub unsupported or only available in Pro Plan?
If it is true in Hub, is there a way to manage trading assets with one or few party with many users?
Or, do I have to register many parties manually at Hub Console?
Hi! The party allocate endpoint in the JSON API is currently unsupported in Daml Hub at all tiers, though we hope to support it in the future. Until then, creating all the parties up-front through the Hub Console is the recommended way to do it at this time
Hello.
Thank you and I have an additional question.
We decided to create all parties through Hub Console manually.
However, when I use the ledger in DAML Hub + json API, I have to manage all access tokens of my customers because my UI server is not in DAML Hub.
In this case, I can access ledger with Hub Service Account, but they also created manually and expired in 30 days.
Is json api able to create and renewal Service Account?
If it cannot, how to manage many parties with json api + external UI service. In B2C service, the number of parties can exceed more than 1000+, and we cannot handle all access tokens of customers (parties) manually.
At this time, there is no API to refresh Service Account credentials automatically after they expire in 30 days.
I have to manage all access tokens of my customers
Generally, we advise against designing your Daml Hub ledger application this way. The ideal production set-up would consist of each user of your application authenticating with separate Daml Hub accounts on the Hub hosted UI. This ensures the best of ledger/contract privacy, security, and ease of use.
The further the app architecture strays from this approach, the less supportable it becomes. For instance, I could imagine that if your main UI is hosted externally, then the Hub hosted page could be a simple login “bridge” that retrieves a user’s party token, and automatically hits a REST endpoint you create in your service, with the token, to redirect and login back to your main UI.
It could work, though I’m not sure I’d personally recommend it. The main point here is creative workarounds might exist, but at best they’d still just be workarounds to how Hub is meant to be used.