Fix links and formatting

WIP

WIP

WIP

WIP

Author: Dan Costello

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

@@ -3,12 +3,13 @@ title: "Customize your login interface"
 slug: "login-interface"
 excerpt: ""
 hidden: false
-metadata: 
-  image: []
-  robots: "index"
+metadata:
+    image: []
+    robots: "index"
 createdAt: "Thu Aug 03 2023 22:56:11 GMT+0000 (Coordinated Universal Time)"
 updatedAt: "Fri Aug 25 2023 21:43:36 GMT+0000 (Coordinated Universal Time)"
 ---
+
 You can customize your login UI in the Login Experience card of the Application Settings Page. This is reached by selecting the Application in the Authentication page. You can preview your changes before you push them to live in the screen preview on the right-hand side.
 
 ## Page order
@@ -17,7 +18,7 @@ To show your social sign on buttons above the email input, select “Social firs
 
 ## Logo and colors
 
-You can add your logo and brand colors in the Login Experience card. We recommend using a square, transparent png file up to XxX pixels. The colors section allows you to configure your button fill, text and border, as well as the background color of your login screen.
+You can add your logo and brand colors in the Login Experience card. We recommend using a square, transparent png file. The colors section allows you to configure your button fill, text and border, as well as the background color of your login screen.
 
 ## Login and sign-up page copy
 
@@ -29,6 +30,6 @@ You can customize the Header, Subheading and Footer copy of the login and signup
 
 The text input for the footer is HTML-enabled, to allow linking out to pages like your Terms of Service or Privacy Policy pages. However, the only accepted HTML elements are:
 
-- **Paragraphs**: `<p>`  `</p>`
-- **Hyperlinks**: `<a>`  `</a>` with the `href` attribute
-- **Line breaks**: `<br>`  `</br>`
+- **Paragraphs**: `<p>` `</p>`
+- **Hyperlinks**: `<a>` `</a>` with the `href` attribute
+- **Line breaks**: `<br>` `</br>`

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

@@ -6,125 +6,153 @@ hidden: false
 createdAt: "Thu Aug 03 2023 22:50:04 GMT+0000 (Coordinated Universal Time)"
 updatedAt: "Thu Jun 06 2024 17:05:49 GMT+0000 (Coordinated Universal Time)"
 ---
+import { Step, Steps } from 'fumadocs-ui/components/steps';
+
 This article details how to use UserClouds to migrate off Auth0 in a few easy steps. It will show you how to migrate 100% of your usernames, profiles, passwords and other login factors off Auth0, without forcing any password resets.
 
 The process should take around 15 minutes to set up. You may then have to wait a few weeks for Auth0 to comply with your ticket request (see step 6). During this time, user profile data will be migrated over in bulk. Users will log in through UserClouds, with UserClouds using Auth0 as an identity provider. When users successfully log in, their credentials will be stored in the UserClouds User Store. As such, the two databases will converge for active users. After a few weeks, Auth0 will provide a static export of your hashed passwords for inactive users, which you can then upload to UserClouds. At this point, you will have successfully migrated all of your user data off Auth0.
 
 The article assumes you have already set up an account, organization, tenant and application in UserClouds. See here for more info. 
 
-## 1. Ready your Auth0 account
-
-### 1a. Create an M2M application in Auth0
-
-First, you need to create an M2M application in Auth0, so that UserClouds's server can call the Auth0 server:
-
-- Log into Auth0 & click Applications in the sidebar
-- Click Create Application.
-- Call your application something like UserClouds Management App
-- Select M2M and hit Create
-- You will be prompted to define permissions. For development purposes, select All and click Authorize. You will be able to narrow this feature set down later - the permissions you allow will depend on the UC feature set that you use.
 
-### 1b. Allow Password Grant Flow
+  ## Ready your Auth0 account
+<Steps>
+  <Step>
+  ### Create an M2M application in Auth0
 
-Next, you need to allow the password grant flow in Auth0. This will let UserClouds capture passwords directly from your end users and verify those passwords with Auth0, rather than redirecting the users themselves to Auth0. This is required to capture any authentication changes for your active users, like new account creations and password resets.
+  First, you need to create an M2M application in Auth0, so that UserClouds's server can call the Auth0 server:
 
-- In Auth0, navigate to your new M2M app’s settings page
-- Click the Settings sub-tab, scroll to the Advanced Settings card and click the Grant Types tab
-- Enable the Password Grant Flow and click Save
+  - Log into Auth0 & click Applications in the sidebar
+  - Click Create Application.
+  - Call your application something like UserClouds Management App
+  - Select M2M and hit Create
 
-### 1c. Configure API Authorization in Auth0
+  - You will be prompted to define permissions. For development purposes, select All and click Authorize. You will be able to narrow this feature set down later - the permissions you allow will depend on the UC feature set that you use.
+  </Step>
+  <Step>
+  ###  Allow Password Grant Flow
 
-These steps assume you use the default database in Auth0. If you use a custom database, and it's not clear how to adapt these steps for that database, contact us at [[email protected].](mailto:[email protected].)
+  Next, you need to allow the password grant flow in Auth0. This will let UserClouds capture passwords directly from your end users and verify those passwords with Auth0, rather than redirecting the users themselves to Auth0. This is required to capture any authentication changes for your active users, like new account creations and password resets.
 
-- Select Settings in the Auth0 Sidebar, and scroll to the API Authorization Settings Card
-- Copy Username-Password-Authentication into the Default Directory field and click Save
+  - In Auth0, navigate to your new M2M app’s settings page
+  - Click the Settings sub-tab, scroll to the Advanced Settings card and click the Grant Types tab
+  - Enable the Password Grant Flow and click Save
+  </Step>
+  <Step>
+  ###  Configure API Authorization in Auth0
 
-## 2. Configure Auth0 as an Identity Provider in UserClouds
+  These steps assume you use the default database in Auth0. If you use a custom database, and it's not clear how to adapt these steps for that database, contact us at [[email protected].](mailto:[email protected].)
 
-### 2a. Create a new Identity Provider in UserClouds
+  - Select Settings in the Auth0 Sidebar, and scroll to the API Authorization Settings Card
+  - Copy Username-Password-Authentication into the Default Directory field and click Save
 
-- In a new tab, go to the UserClouds Console and select your tenant
-- Navigate to the Authentication page and scroll down to Identity Platforms: Migrations & Back-Ups card
-- Click Create Provider
+  </Step>
+</Steps>
 
-### 2b. Change your provider type to Auth0
+## Configure Auth0 as an Identity Provider in UserClouds
+<Steps>
+  <Step>
 
-- Select the provider you just created
-- Rename the provider something like Auth0 App Connection  
-  Change the type to Auth0
+  ### Create a new Identity Provider in UserClouds
 
-### 2c. Copy over your Auth0 Provider Settings from Auth0
+  - In a new tab, go to the UserClouds Console and select your tenant
+  - Navigate to the Authentication page and scroll down to Identity Platforms: Migrations & Back-Ups card
+  - Click Create Provider
+  </Step>
+  <Step>
+  ### Change your provider type to Auth0
 
-- Back in your Auth0 tab, open the App page for your M2M app (which you called something like UserClouds Management App)
-- Navigate to the Settings sub-tab and copy across the Domain, Client ID and Client Secret into the equivalent fields in UserClouds
-- On the same Auth0 page, navigate to the APIs sub-tab, click the Auth0 Management API, and scroll down to the General Settings section
-- Copy the Identifier field and paste it into the Audience field in the Auth0 Provider Settings card in UserClouds
-- Click Save
+  - Select the provider you just created
+  - Rename the provider something like Auth0 App Connection  
+    Change the type to Auth0
+  </Step>
+  <Step>
+  ### Copy over your Auth0 Provider Settings from Auth0
 
-## 3. Import your Auth0 applications to UserClouds
-
-### 3a. Import your applications
+  - Back in your Auth0 tab, open the App page for your M2M app (which you called something like UserClouds Management App)
+  - Navigate to the Settings sub-tab and copy across the Domain, Client ID and Client Secret into the equivalent fields in UserClouds
+  - On the same Auth0 page, navigate to the APIs sub-tab, click the Auth0 Management API, and scroll down to the General Settings section
+  - Copy the Identifier field and paste it into the Audience field in the Auth0 Provider Settings card in UserClouds
+  - Click Save
+  </Step>
+</Steps>
 
+## Import your Auth0 applications to UserClouds
+<Steps>
+<Step>
+### Import your applications
 - In the same UserClouds page, scroll to the bottom card Import from Auth0 and click Import from Auth0
 - This will import your Auth0 app configurations (like Client ID/Secret and Login URIs) into UserClouds
 - The sync may take a moment - so refresh your page if you don't see any feedback immediately
-
-### 3b. Review your application configurations
+</Step>
+<Step>
+### Review your application configurations
 
 - Next, it's beneficial to check your Auth0 configurations have successfully replicated in UserClouds, since you may be using an advanced configuration setting that UserClouds does not support migration for yet.
 - Navigate to each UserClouds Application's page (UserClouds > Authentication > Login Application) and review the settings
 - _If you are concerned your settings have not successfully ported over, please email [[email protected]](mailto:[email protected])_
-
-## 4. Make Auth0 your active provider
+</Step>
+<Step>
+## Make Auth0 your active provider
 
 - In UserClouds, navigate to the Authentication Page
 - Scroll to the Identity Platforms: Migrations & Back-Ups card
 - Set Auth0 to active provider and click Save
 
 At this point, UserClouds will begin syncing your user profiles from Auth0. You will see your users appear in the End Users page in UserClouds. Passwords will not sync at this point.  
-
-## 5. Begin authenticating your users via UserClouds
+</Step>
+</Steps>
+## Begin authenticating your users via UserClouds
 
 Now you are ready to start authenticating your users via UserClouds. For more info on adding UserClouds to your software, see the previous article.
 
 UserClouds will now begin syncing passwords for active users. When a user is logged in, they will log in via a UserClouds page, which will send the login credentials to the active provider (Auth0). If the login succeeds, the credentials will be stored in the UserClouds User Store. 
 
-## 6. Gather non-active users / passwords from Auth0
+## Gather non-active users / passwords from Auth0
 
-### 6a. Submit an Auth0 support ticket for salted / hashed passwords
+<Steps>
+<Step>
+### Submit an Auth0 support ticket for salted / hashed passwords
 
 - Go to the Auth0 support portal
 - Submit a ticket requesting to export your hashed, salted passwords and MFA secrets for the relevant tenant, and requesting the hashing algorithms
 - Respond to Auth0's support team confirming you want to export all hashed passwords and MFA secrets  
   Complete any other account verification steps
-
-### 6b. Wait for Auth0 customer service
+</Step>
+<Step>
+### Wait for Auth0 customer service
 
 Auth0 can be slow here, so this step may take up to a few weeks. After this period, Auth0 will share your login data, correct as of the date that they ran your export. UserClouds will capture any authentication changes after this time (like new users or password resets), via Step 5.
-
-### 6c. Import hashed password data to UserClouds
+</Step>
+<Step>
+### Import hashed password data to UserClouds
 
 Once Auth0 has shared your customer password data, you can upload it to UserClouds. Docs coming soon! For help, please email [[email protected].](mailto:[email protected].)
 
 The UserClouds User Store now has all the login data of your inactive users (whose credentials are unchanged since the Auth0 export) and your active users (whose credentials were captured in Step 5). You have successfully exported all your user data from Auth0, without forcing any users to reset their password. 
+  </Step>
+</Steps>
 
-## 7. Switch your active provider back to UserClouds
+## Switch your active provider back to UserClouds
 
 The final step is to switch your active provider back to UserClouds. This must be done at the tenant- and app-level.
-
-### 7a. Switch your tenant's active provider to UserClouds
+<Steps>
+<Step>
+### Switch your tenant's active provider to UserClouds
 
 - In UserClouds, navigate to the Authentication Page
 - Scroll to the Identity Platforms: Migrations & Back-Ups card
 - Set Auth0 to active provider and click Save
-
-### 7b. Switch your apps' active providers to UserClouds
+</Step>
+<Step>
+### Switch your apps' active providers to UserClouds
 
 - In UserClouds, navigate to the Authentication Page
 - 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
-
+</Step>
+</Steps>
 Hooray! You did it. You successfully migrated off Auth0.

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

@@ -9,25 +9,32 @@ metadata:
 createdAt: "Thu Aug 03 2023 22:41:51 GMT+0000 (Coordinated Universal Time)"
 updatedAt: "Fri Aug 25 2023 21:46:36 GMT+0000 (Coordinated Universal Time)"
 ---
-## 1. Create an account
+import { Step, Steps } from 'fumadocs-ui/components/steps';
 
-UserClouds is invite-only right now. If you don’t have an invite, please email [[email protected].](mailto:[email protected].) Click the link in your email invite and create a username and password. Congrats! You’ve now experienced UserClouds as an end-user.
+<Steps>
+  <Step>
+  ## Create an account
 
-## 2. Name your organization and tenant
+  UserClouds is invite-only right now. If you don’t have an invite, please email [[email protected].](mailto:[email protected].) Click the link in your email invite and create a username and password. Congrats! You’ve now experienced UserClouds as an end-user.
+  </Step>
+  <Step>
+  ## Name your organization and tenant
 
-If you’re setting up your company’s account with UserClouds, you’ll be prompted to name your organization and your first tenant.
+  If you’re setting up your company’s account with UserClouds, you’ll be prompted to name your organization and your first tenant.
 
-- **A company** is a collection of users and tenants. It allows you to group applications together and collaborate with team-mates. Typically, customers set up one organization for their company.
-- **A tenant** is a single instance of UserClouds's tech (APIs, user store etc). Each tenant can handle multiple applications. Typically, customers set up one tenant per environment (e.g.. dev / testing / production). We also see enterprise-facing companies create a separate tenant for each one of their customers if/where they need data isolation.
+  - **A company** is a collection of users and tenants. It allows you to group applications together and collaborate with team-mates. Typically, customers set up one organization for their company.
+  - **A tenant** is a single instance of UserClouds's tech (APIs, user store etc). Each tenant can handle multiple applications. Typically, customers set up one tenant per environment (e.g.. dev / testing / production). We also see enterprise-facing companies create a separate tenant for each one of their customers if/where they need data isolation.
+  </Step>
+  <Step>
+  ## Rename your application
 
-## 3. Rename your application
+  You’ll land on the Authentication Page for your Tenant in UserClouds. This is where you can configure your tenant’s applications, underlying IDPs, Social and 3rd Party IDPs and settings.
 
-You’ll land on the Authentication Page for your Tenant in UserClouds. This is where you can configure your tenant’s applications, underlying IDPs, Social and 3rd Party IDPs and settings.
+  UserClouds automatically creates a Default Application for each tenant.
 
-UserClouds automatically creates a Default Application for each tenant.
-
-- **An application** is a single OAuth2 client that can call the APIs of any IDPs configured in your tenant (e.g. primary - Auth0, back-up - Plex, third party - social). It is where you will configure how authentication works for your project. For example, you might configure the application to require two factor authentication via SMS or offer passwordless login.
-
-To rename your application, click into the application, hit edit, change the name, and click Save. In UserClouds, you must always click Save to commit your changes.
+  - **An application** is a single OAuth2 client that can call the APIs of any IDPs configured in your tenant (e.g. primary - Auth0, back-up - Plex, third party - social). It is where you will configure how authentication works for your project. For example, you might configure the application to require two factor authentication via SMS or offer passwordless login.
 
+  To rename your application, click into the application, hit edit, change the name, and click Save. In UserClouds, you must always click Save to commit your changes.
+  </Step>
+</Steps>
 Hooray! You created your first application in UserClouds. Now let’s see how to add UserClouds to your software.