80 lines
3.5 KiB
Plaintext
80 lines
3.5 KiB
Plaintext
---
|
|
title: Quick Start
|
|
description: Learn how to use Duckity in some minutes.
|
|
icon: Zap
|
|
---
|
|
|
|
Getting started with Duckity is quite simple. Head over to
|
|
[Duckity's Dashboard](https://app.duckity.com/) and log in using your favorite method. If it's your
|
|
first time logging in, your account will be automatically created.
|
|
|
|
## Create an Application [step]
|
|
|
|
Duckity is divided into one or more applications within your account. You create one application per
|
|
project in which you want to integrate Duckity. To create a new application, press on the yellow **+
|
|
New Application** button at the top right corner of the screen.
|
|
|
|
Once you've set the name of it, press on the **✓ Create Application** button. Congratulations! You
|
|
now have your first application created.
|
|
|
|
<Callout>
|
|
Additionally, in case your application is a web app, you can set up the CORS origins to fit your
|
|
application's origins. For example, if you'll be protecting the login form of your app hosted at
|
|
`https://example.com/login`, add `https://example.com` (scheme and host, no path) to your app's
|
|
origins. If your application is not a web app, you can leave the CORS origins empty.
|
|
</Callout>
|
|
|
|
## Create a Protection Profile [step]
|
|
|
|
Applications commonly have multiple features that need to be protected. For example, you may have a
|
|
signup form and a login form with different protection needs. For each, you'll create one
|
|
**protection profile** with settings tuned to each feature's specific needs.
|
|
|
|
Each application needs at least one protection profile to work. To create your first one, press the
|
|
**+ Create Protection Profile** button.
|
|
|
|
Set the name to the name of the feature you'll be protecting, like "Sign-up Form" or "Add Friend".
|
|
This is for you to recognize it later, it won't be displayed to your users. Once you're done filling
|
|
it, press on **✓ Create Protection Profile**.
|
|
|
|
Copy your protection profile's ID using the button at the top right corner, that's all you'll need
|
|
to integrate it into your application.
|
|
|
|
<Callout>
|
|
Don't worry about all the settings displayed for now, you'll learn to tune them later.
|
|
</Callout>
|
|
|
|
## Install an SDK [step]
|
|
|
|
To integrate your protection profile with your application, you'll need a client-side SDK and a
|
|
server-side SDK.
|
|
|
|
Duckity has multiple official SDKs for you to plug and play.
|
|
|
|
import { SiC, SiJavascript, SiPython, SiRust, SiReact } from "@icons-pack/react-simple-icons";
|
|
|
|
<Cards>
|
|
<Card href="/sdks/javascript" title="JavaScript" icon={<SiJavascript />}>
|
|
Integrate Duckity into your application using the JavaScript SDK.
|
|
</Card>
|
|
<Card href="/sdks/react" title="React" icon={<SiReact />}>
|
|
Integrate Duckity into your React app using the React SDK.
|
|
</Card>
|
|
<Card href="/sdks/python" title="Python 3" icon={<SiPython />}>
|
|
Integrate Duckity into your application using the Python SDK.
|
|
</Card>
|
|
<Card href="/sdks/rust" title="Rust" icon={<SiRust />}>
|
|
Integrate Duckity into your application using the Rust SDK. Supports no-std environments.
|
|
</Card>
|
|
</Cards>
|
|
|
|
In case we don't have a client SDK for your language yet, you can use the C SDK. It's written in
|
|
Rust, you can link to it through the exposed C API, and it wraps all the required encoding and
|
|
decoding in a simple API. You may also find the following guide useful:
|
|
|
|
import { FileCodeCorner } from "lucide-react";
|
|
|
|
<Card title="Write Your Own SDK" icon={<FileCodeCorner />} href="/guides/write-your-own-sdk">
|
|
Learn how to write your own SDK in any language.
|
|
</Card>
|