Arshad Noor posted a comment on ticket #1

FIDO protocols are designed to only work with web-origins for which they are configured. So, if a Magento instance is running at www.example.com, then the FIDO server serving that instance will only allow keys to be registered and used for example.com. However, if there is a site that uses 3 Magento instances - example.com, happyday.com and greatwidgets.com - wishes to use a single FIDO server, then the app.json file must include all three origins when using that FIDO server. You are not sending...

JERIN CHERIAN modified a comment on ticket #1

Hi, Arshad,does that mean, I will have to change my app.json file of the server,everytime I change my magento instance ? Shouldnt the server register the keys according to the url that we send to the server ?

JERIN CHERIAN posted a comment on ticket #1

Hi, Arshad,does that mean, I will have to change my app.json file of the server,everytime I change my magento instance ?

Arshad Noor posted a comment on ticket #1

Hi Jerin, The problem is that you're running the FIDO server with the default appid, which is pointing to "https://demo.strongauth.com:8181/app.json". This will only work if the Magento instance was running on strongauth.com. In order to make this work with your Magento instance - which is probably running on a different URL origin, you have to modify the app.json file of your FIDO server configuration to your DNS top-level-domain + 1 (TLD+1) value, restart the FIDO server and then attempt to register...

JERIN CHERIAN created ticket #1

Cannot register a new device while integrating as a module

Michael Ishimoto committed [r3]

Edited the default FIDO server from an internal testing FIDO server to the publicly available FIDO server at demo.strongauth.com

magfido released /StrongAuth-Magento-FIDO-Integration-v1.1.pdf

Arshad Noor committed [r2]

Initial import

Arshad Noor committed [r1]

Add initial directories