Getting Started with OKX AA WebAuthn Demo

WebAuthn Steps

Create passkey

1. Server returns attestation options
2. Client send create passkey request per returned attestation options to authenticator
3. Authenticator returns attestation result to client
4. Client send attestation result to server
5. Server validates challenge, origin, factor
6. Server responses to client the validation is successfully or not

Signing using passkey

1. Server returns assertion options
2. Client send get passkey request per returned assertion options to authenticator
3. Authenticator returns assertion result with signature to client
4. Client send assertion result with signature to server
5. Server validates challenge, origin, factor, public key, signature, prevCounter and optionally userHandle
6. Server responses to client the validation is successfully or not

Link references

1. FIDO Passkeys
2. WebAuthn Guide
3. Passwordless login with passkeys
4. Passkeys developer guide for relying parties
5. Passkey support on different platforms
6. Configure WebAuthn with Device Biometrics for MFA
7. WebAuthn Spec
8. WebAuthn FIDO2 Library
9. ECDSA mathematics explanation
10. COSE parsing

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can't go back!

If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.

You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.