We removed device_name & device_uuid from the Mobile SDK.
However, for providing better UX, you can choose to capture and store them on YOUR server.
If you do capture them, please make sure that your application’s GDPR complience is not violated.
We shall update the documentation soon. Thanks for pointing it out
quick question in building up the test sdk on this part of the instructions to build build a demo wallet where does this file go
v). Adding SDK configuration file
Create OstWalletSdk.plist file. This file has configuration attributes used by OstWalletSdk. You should copy paste the configuration values from below snippet.
does it go into xcode as a snipet or am i making a plist file to go in a folder somewhere.
im sure its me i just need to be clear
Hi, we've been working on making Brand Token setup minting and distributing as easy possible for OST Platform customers, including ways to make it risk free to get started with minimal investment. This involves both technology and business/financial decisions. We've also been gathering direct input and feedback from OST clients and prospects on various facets Brand Token minting. And, we've been developing token rules and logic to help aid this, to accomplish the needs and desires of real clients.
As @benjaminbollen points out, we'll release specs when ready. And, OST will not be a custodial service.
Yes, you are correct. The passphrasePrefix must only be fetched when needed.
The security guidelines are provided here:
On a side note, all device-manager operations need user authentication.
User is authenticated using biometric OR they can enter the active pin.
As pin is never (and should never be) stored in it's raw form even in the application, we need need passphrasePrefix to regenerate the pin to key to authentication.
In current state, the demo-app is only meant for testing the Sdk.
Hi @daan-ost ,
Thanks for reporting the issue.
I request you to kindly send us the parameters of OstWalletSdk.activateUser method.
In general, this error signifies that the device failed to create a recovery key based on given inputs.
The recovery key is never stored anywhere and only created when needed.
To create recovery key, we use:
userPin - from user
passphrasePrefix - this should come from your server (associated with the user and must not change/rotate)
SCrypt salt - This is provided by Ost Platform