Skip to content

Commit fb1f0de

Browse files
author
Dan Costello
authored
Formatting and colons (#9)
* Formatting * Dash to colon
1 parent e306f86 commit fb1f0de

File tree

13 files changed

+183
-155
lines changed

13 files changed

+183
-155
lines changed

content/docs/guides/(authentication)/how-to-guides/authentication-methods.mdx

Lines changed: 32 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,14 @@ slug: "authentication-methods"
44
excerpt: ""
55
hidden: false
66
metadata:
7-
image: []
8-
robots: "index"
7+
image: []
8+
robots: "index"
99
createdAt: "Thu Aug 03 2023 22:51:23 GMT+0000 (Coordinated Universal Time)"
1010
updatedAt: "Fri Aug 25 2023 21:43:12 GMT+0000 (Coordinated Universal Time)"
1111
---
1212

13+
import { Step, Steps } from "fumadocs-ui/components/steps";
14+
1315
UserClouds supports every major method of authentication, such as social sign in with Google, Facebook and LinkedIn OAuth. The user's accounts will be owned by the Identity Platforms configured in “Underlying Identity Providers”.
1416

1517
Adding a Social/Third Party Connection to a login flow can be completed in three steps:
@@ -18,28 +20,39 @@ Adding a Social/Third Party Connection to a login flow can be completed in three
1820
2. Connect your tenant to your third party account
1921
3. Turn on that authentication method in your application
2022

21-
## 1. Configure your account with the third party.
23+
<Steps>
24+
<Step>
25+
## Configure your account with the third party.
26+
27+
To set up third party OAuth for the first time, you'll need to create your account with the third party providers directly. For more info on this, see the articles below:
28+
29+
- [Setting up Google OAuth](https://support.google.com/cloud/answer/6158849?hl=en)
30+
- [Setting up Facebook OAuth](https://developers.facebook.com/docs/facebook-login)
31+
- [Setting up Apple OAuth](https://developer.apple.com/sign-in-with-apple/get-started/)
32+
33+
</Step>
34+
<Step>
35+
## Connect your tenant to the third party.
2236

23-
To set up third party OAuth for the first time, you'll need to create your account with the third party providers directly. For more info on this, see the articles below:
37+
Once you have set up your relationship with the third party OAuth provider, it's time to connect your tenant to that provider:
2438

25-
- [Setting up Google OAuth](https://support.google.com/cloud/answer/6158849?hl=en)
26-
- [Setting up Facebook OAuth](https://developers.facebook.com/docs/facebook-login)
27-
- [Setting up Apple OAuth](https://developer.apple.com/sign-in-with-apple/get-started/)
39+
- Go to your Tenant’s Authentication page.
40+
- Select the relevant provider in the Social & 3rd Party Identity Providers card
41+
- Copy over your OAuth Client ID and Client Secret
42+
- Click Save!
2843

29-
## 2. Connect your tenant to the third party.
44+
</Step>
45+
<Step>
3046

31-
Once you have set up your relationship with the third party OAuth provider, it's time to connect your tenant to that provider:
47+
## Turn on the authentication method in your application.
3248

33-
- Go to your Tenant’s Authentication page.
34-
- Select the relevant provider in the Social & 3rd Party Identity Providers card
35-
- Copy over your OAuth Client ID and Client Secret
36-
- Click Save!
49+
Now your tenant is connected to the third party, you can add their authentication method to any applications within that tenant. This allows you to serve different login experiences to different users within the same tenant. For example, Uber might prefer to have drivers and riders served by the same tenant, since a driver wants their password to work for both apps. But Uber might also require 2FA for the driver app, since drivers payouts are configured through the driver app.
3750

38-
## 3. Turn on the authentication method in your application.
51+
1. Navigate to the Application page (Select Tenant > Authentication > Application).
52+
2. Create social redirect and logout URIs for that application, e.g. `https://tenantname.tenant.userclouds.com/social/callback`
53+
3. Add these URIs to your account with the third party (see links in part 1).
54+
4. Select which authentication methods are enabled in the Login Settings card. You can also configure other authentication methods, like Passwordless / Magic Link, from this card.
3955

40-
Now your tenant is connected to the third party, you can add their authentication method to any applications within that tenant. This allows you to serve different login experiences to different users within the same tenant. For example, Uber might prefer to have drivers and riders served by the same tenant, since a driver wants their password to work for both apps. But Uber might also require 2FA for the driver app, since drivers payouts are configured through the driver app.
56+
</Step>
4157

42-
1. Navigate to the Application page (Select Tenant > Authentication > Application).
43-
2. Create social redirect and logout URIs for that application, e.g. `https://tenantname.tenant.userclouds.com/social/callback`
44-
3. Add these URIs to your account with the third party (see links in part 1).
45-
4. Select which authentication methods are enabled in the Login Settings card. You can also configure other authentication methods, like Passwordless / Magic Link, from this card.
58+
</Steps>

content/docs/guides/(authentication)/how-to-guides/migrate-from-auth0.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,11 @@ The final step is to switch your active provider back to UserClouds. This must b
156156
### Switch your apps' active providers to UserClouds
157157

158158
- In UserClouds, navigate to the Authentication Page
159-
- For each app - Click the app to go into the Application page - In the General Settings card, open the Underlying Identity Provider Apps accordion section - Check the box for your tenant's UserClouds IDP - Click Save
159+
- For each app
160+
1) Click the app to go into the Application page
161+
2) In the General Settings card, open the Underlying Identity Provider Apps accordion section
162+
3) Check the box for your tenant's UserClouds IDP
163+
4) Click Save
160164
</Step>
161165
</Steps>
162166
You did it! You successfully migrated off Auth0.

content/docs/guides/(authentication)/quickstart-guides/add-userclouds-to-your-software.mdx

Lines changed: 20 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,24 +7,34 @@ createdAt: "Thu Aug 03 2023 22:43:44 GMT+0000 (Coordinated Universal Time)"
77
updatedAt: "Mon Nov 04 2024 20:08:29 GMT+0000 (Coordinated Universal Time)"
88
---
99

10+
import { Step, Steps } from "fumadocs-ui/components/steps";
11+
1012
You’ve already created your first application in UserClouds. Nice job! This page shows how to set up UserClouds Authentication on your software.
1113

12-
## 1. Specify your allowed Redirect and Logout URLs
14+
<Steps>
15+
<Step>
1316

14-
In the UserClouds Console, select your tenant, then navigate to Authentication > Login Apps via the sidebar. Select your Default Application to access this Application’s Settings page. From here, you can specify the exact URLs you want to allow as:
17+
## Specify your allowed Redirect and Logout URLs
1518

16-
- OIDC/OAuth2 callback URLs: this is where UserClouds will redirect your user to after they authenticate.
17-
- Auth logout URLs: this is where UserClouds will redirect your user to after they log out.
19+
In the UserClouds Console, select your tenant, then navigate to Authentication > Login Apps via the sidebar. Select your Default Application to access this Application’s Settings page. From here, you can specify the exact URLs you want to allow as:
1820

19-
Remember to click Save to apply this change!
21+
- OIDC/OAuth2 callback URLs: this is where UserClouds will redirect your user to after they authenticate.
22+
- Auth logout URLs: this is where UserClouds will redirect your user to after they log out.
2023

21-
## 2. Cut and paste your UserClouds settings into the sample app code
24+
Remember to click Save to apply this change!
2225

23-
Each UserClouds application has four key attributes: an application ID, an application name, a client ID and a client secret. You will need your Client ID and Client Secret, when you use your TenantURL to call UserClouds's APIs.
24-
Before you use the sample code elsewhere, make sure you replace the sample app’s instances of these variables with your application’s attributes. You can find these on your Application’s Settings page.
26+
</Step>
27+
<Step>
28+
## Cut and paste your UserClouds settings into the sample app code
2529

26-
## 3. Implement UserClouds in your software
30+
Each UserClouds application has four key attributes: an application ID, an application name, a client ID and a client secret. You will need your Client ID and Client Secret, when you use your TenantURL to call UserClouds's APIs.
31+
Before you use the sample code elsewhere, make sure you replace the sample app’s instances of these variables with your application’s attributes. You can find these on your Application’s Settings page.
32+
</Step>
33+
<Step>
34+
## Implement UserClouds in your software
2735

28-
Use the sample code (or any other OIDC library you like) as a template to add UserClouds to your application.
36+
Use the sample code (or any other OIDC library you like) as a template to add UserClouds to your application.
37+
</Step>
38+
</Steps>
2939

3040
Great job! You’re all set up.

content/docs/guides/(data-access)/definitions/access-policies.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ In addition, two special types of access policies are available:
2020
- **Column Default Access Policies**: These policies are associated with specific columns and are applied by default to all reads that extract data from those columns. They ensure consistent application of access rules for sensitive data, such as automatically applying a role check to the SSN column. They can be overridden for individual accessors. Learn more [here](/docs/protect-a-column-with-defaults).
2121
- **Global Baseline Access Policies**: These policies are applied by default to all reads, providing a consistent security baseline. For example, a global policy might always require a valid token or restrict access to trusted IP addresses. They cannot be overridden. Learn more [here](/docs/apply-global-protection-policies).
2222

23-
Access policies provide central, fine-grained control over sensitive data access. They can evaluate purpose, identity, authorization, location, , and more. They can range from simple "always allow resolution" policies to complex evaluations.
23+
Access policies provide central, fine-grained control over sensitive data access. They can evaluate purpose, identity, authorization, location, and more. They can range from simple "always allow resolution" policies to complex evaluations.
2424

2525
![Access policies give you central, fine-grained control over sensitive data access. Policies can evaluate purpose, identity, permissions, location, expiration timelines, rate limits and more.](/assets/images/flow-chart.webp)
2626

0 commit comments

Comments
 (0)