This is difficult to explain but I will do my best.
The current process requires that the user subscribe to an app via a public key. After the user subscribes, an app is expected to save a unique token key, the secure url, and some other irrelevant information. The store that subscribes does not have access to the unique token key, how do I verify that the user using my app is legitimately the one who subscribed? The user should be able to access their unique token key as a password to verify their identity within the app which will greatly reduce the risk of someone who might happen to put in the correct SecureURL and the publicly available public key and being able to access customer, order, etc data. A private key doesn't do anything for me if the user can't use it to verify their account.
Hope it makes sense!
Mike C.
The current process requires that the user subscribe to an app via a public key. After the user subscribes, an app is expected to save a unique token key, the secure url, and some other irrelevant information. The store that subscribes does not have access to the unique token key, how do I verify that the user using my app is legitimately the one who subscribed? The user should be able to access their unique token key as a password to verify their identity within the app which will greatly reduce the risk of someone who might happen to put in the correct SecureURL and the publicly available public key and being able to access customer, order, etc data. A private key doesn't do anything for me if the user can't use it to verify their account.
Hope it makes sense!
Mike C.
Comment