- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 May 2018 00:12:27 +0000
- To: public-webauthn@w3.org
I don't think I fully understand your use case, but the general idea is that whatever runs on the client side is controlled by the user, and any security checks in that code can therefore be bypassed. It doesn't quite sound like that's what you're describing, though. Did I get this right? 1. Alice logs in and proves she's an admin (e.g. by signing a challenge generated on the server, which is then verified on the server). 2. Alice uses client side script to generate a JWT. 3. Client side script uses Alice's public key credential to sign the JWT. 4. JWT with Alice's admin signature is sent to ordinary user Bob. 5. Bob sends signed JWT to server, and receives a perk. If that's what you're describing, I _think_ that sounds reasonable enough. In this case you have the additional assumption that Alice is not evil (because she's an admin, and her signatures prove that) -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/902#issuecomment-388222432 using your GitHub account
Received on Friday, 11 May 2018 00:12:34 UTC