Frederik Rothenberger

@MasterKale: Unfortunately, the webauthn functionality is now broken completely when using Safari 15.6.1 (i.e. I could not find any combination of settings that allowed me to register successfully). I only...

@domwoe: No, this is not expected. Also, this example does not use our recommended dev setup using Internet Identity (documented here: https://github.com/dfinity/internet-identity/tree/main/demos/using-dev-build). The newer dev builds of II are smaller...

This is a very nice feature, that we're looking forward to using. 🙂 So far, the following issues are blockers for us: * The derived traits should be configurable (i.e...

Also: this is a very cool project. Thanks for doing this!

This excludes already registered devices. I.e. it prevents creating a new credential if an existing one is already available on the same WebAuthn `Authenticator`. So you cannot register TouchId twice...

@nmattia: No, the excluded credential id's are the ones of the anchor you're trying to add a device to. So, when adding something to anchor 10000 you don't exclude any...

Hi @neokree > Sorry but I don't think I understood why a certified HTTP headers is necessary here.. Maybe with the roadmap doc I can see the challenge better. Unfortunately,...

Unfortunately, the initial design we had does not work in practice. We would need to invest some more research time to finalize the design, however II research is very much...

Hi @FrankC01 Is this questions about interacting with II from IoT devices? The only requirement to interact with Internet Identity is to be able to make canister calls and sign...

Thanks @FrankC01 for the clarification. However, I'm not sure that Internet Identity is the correct tool for the job. II is an identity provider intended for active clients that need...