Problem with Following the Sample Scenarios

[NikolaVetnic]

Hello there,

I am having trouble following the sample scenarios in both the local setup and the setup you provide.

The results of following these two scenarios can be viewed here:

• Problem with Scenario #1,
• Problem with Scenario #2, the problem persists regardless of the option selected in the app.

I have also tried the local setup as suggested here, but the problem in that case is probably that I cannot sign up while offline, while signing up using your "live" setup leads to the problem shown above. Here is what I tried:

• Problem with local setup.

And another thing, if I may - is there any kind of API documentation as to what endpoints are offered by the backend server (or some other service you are providing) that could potentially be accessed without your own frontend app?

Looking forward to your answers, I really like what I am seeing so far 😄

[gkatrakazas]

Could you please tell us the version of macOS and Safari you are currently using?

[NikolaVetnic]

Thank you for the prompt reply!

Sure, it's MacOS 15.1.1 (24B91) and Firefox 133.0.3 (aarch64), I did not try it in Safari.

[gkatrakazas]

Currently, Firefox does not support the PRF extension. We recommend using other browsers such as Chrome, Edge, Opera, or Safari for full functionality. For more details on PRF compatibility across various operating systems and browsers, please visit our documentation here.

[NikolaVetnic]

This is what I get on Chrome when I try to follow the first scenario and attempt to sign up:

This browser or security key is not supported. Please make sure that your browser supports the WebAuthn PRF extension and your security key, if any, supports the "hmac-secret" extension. [Learn more here](https://github.com/wwWallet/wallet-frontend#prf-compatibility).

I will now try the Safari.

UPDATE: Works with Safari, thanks.

[NikolaVetnic]

Would you also be so kind as to direct me to any kind of information source regarding this:

And another thing, if I may - is there any kind of API documentation as to what endpoints are offered by the backend server (or some other service you are providing) that could potentially be accessed without your own frontend app?

[gkatrakazas]

If you see the prf table, on macOS you are tring with Internal on chrome, that's the reason you failed now.
You can you any other way with ✅ to signup!

[NikolaVetnic]

One more question - do you have any advice when running the docker compose locally, since there is no option to sign up there and I have to use the telephone to log in via the QR code?

[gkatrakazas]

Do you mean when you are offline ?

[NikolaVetnic]

Precisely, when I am running the whole project via Docker on my local machine.

[gkatrakazas]

As i saw in the video, you don't have the latest master of the frontend. There was an issue in previous versions about the Online/Offline detection, so i am not really sure about the exact reason of the wrong offline!

[NikolaVetnic]

The problem was actually with the backend server. From what I gather, you are mounting source files into the container to enable hot reload among other things, and there was an issue with file permissions which I solved by calling chmod -R 0777 on the entire ecosystem folder. Now it works and I can even fiddle with the enterprise part of the solution.

In regards to modifying your supplied issuers and the verifier, should I write to you in this issue, or create another?

[gkatrakazas]

I recommend creating a new issue for better tracking and clarity.