forked from FusionAuth/fusionauth-site
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix spelling errors jun 18 2024 round 2 (FusionAuth#3126)
* have db table be shown as code so that spellcheck doesn't barf on the all the hash strings * more known words * Added index pages to these integrations sections, mostly so the title would be cased correctly * fixed typos
- Loading branch information
Showing
8 changed files
with
100 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
19 changes: 19 additions & 0 deletions
19
astro/src/content/docs/lifecycle/authenticate-users/integrations/oidc/index.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| --- | ||
| title: Overview | ||
| description: Examples of OIDC integrations. | ||
| navcategory: login-methods | ||
| section: lifecycle | ||
| subcategory: authenticate users | ||
| tertcategory: integrations | ||
| quatercategory: oidc | ||
| topOfNav: true | ||
| --- | ||
|
|
||
| While OpenID Connect (OIDC) is a standard and is broadly interoperable, this section contains examples of integrations where external applications delegate to FusionAuth for user authentication. | ||
|
|
||
| ## Examples | ||
|
|
||
| * [CockroachDB](/docs/lifecycle/authenticate-users/integrations/oidc/cockroachdb) | ||
| * [Salesforce](/docs/lifecycle/authenticate-users/integrations/oidc/salesforce) | ||
|
|
||
| This is not the limit of supported OIDC Relying Parties (RPs). The FusionAuth community has integrated FusionAuth with many others. If you have questions about support for a specific RP, please [contact us](/contact). |
22 changes: 22 additions & 0 deletions
22
astro/src/content/docs/lifecycle/authenticate-users/integrations/saml/index.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| --- | ||
| title: Overview | ||
| description: Examples of SAMLv2 integrations. | ||
| navcategory: login-methods | ||
| section: lifecycle | ||
| subcategory: authenticate users | ||
| tertcategory: integrations | ||
| quatercategory: saml | ||
| --- | ||
|
|
||
| While Security Assertion Markup Language (SAMLv2) is a standard and is broadly interoperable, this section contains examples of integrations where external applications delegate to FusionAuth for user authentication. | ||
|
|
||
| ## Examples | ||
|
|
||
| * [Aiven](/docs/lifecycle/authenticate-users/integrations/saml/aiven) | ||
| * [Google](/docs/lifecycle/authenticate-users/integrations/saml/google) | ||
| * [Pagerduty](/docs/lifecycle/authenticate-users/integrations/saml/pagerduty) | ||
| * [SendGrid](/docs/lifecycle/authenticate-users/integrations/saml/sendgrid) | ||
| * [Tableau Cloud](/docs/lifecycle/authenticate-users/integrations/saml/tableau-cloud) | ||
| * [Zendesk](/docs/lifecycle/authenticate-users/integrations/saml/zendesk) | ||
|
|
||
| This is not the limit of supported SAML Service Providers (SPs). The FusionAuth community has integrated FusionAuth with many others. If you have questions about support for a specific SP, please [contact us](/contact). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -30,7 +30,7 @@ export const script_supports_social_logins = 'true'; | |
|
|
||
| This document will help you migrate users from Stytch to FusionAuth. | ||
|
|
||
| There are a number of different ways applications can be integrated with Stych, and it would be difficult to cover them all. This guide is a low-level, technical tutorial focusing on transferring password hashes, calling APIs, and preparing data when migrating users from a Consumer Authentication project. The steps outlined here have not been tested with the Stytch B2B SaaS Authentication project type. | ||
| There are a number of different ways applications can be integrated with Stytch, and it would be difficult to cover them all. This guide is a low-level, technical tutorial focusing on transferring password hashes, calling APIs, and preparing data when migrating users from a Consumer Authentication project. The steps outlined here have not been tested with the Stytch B2B SaaS Authentication project type. | ||
|
|
||
| This guide explains how to import passwords into FusionAuth, but does not deal with other Stytch authentication types like magic links, passkeys, passcodes, mobile biometrics, two-factor authentication, and social logins such as Google OAuth. | ||
|
|
||
|
|
@@ -104,7 +104,7 @@ Create three example users: | |
| - If any errors occur and you need to delete the users, uncomment the lines with `client.users.delete`, set the user Ids from the dashboard, and rerun the script. | ||
|
|
||
| <Aside type="note"> | ||
| The `1_makeStytchUsers.mjs` file uses the Stytch JavaScript SDK to create users with three different hashing algorithms. However, the line `client.passwords.authenticate` provides the cleartext password to Stytch, which Stytch uses to rehash the user password using the Scrypt hashing algorithm. At the end of this script, all your users' passwords will be hashed with Scrypt in the Stytch database. | ||
| The `1_makeStytchUsers.mjs` file uses the Stytch JavaScript SDK to create users with three different hashing algorithms. However, the line `client.passwords.authenticate` provides the clear text password to Stytch, which Stytch uses to rehash the user password using the Scrypt hashing algorithm. At the end of this script, all your users' passwords will be hashed with Scrypt in the Stytch database. | ||
| Even though you can create passwords for Stytch users with different hashing algorithms ([bcrypt, scrypt, Argon2, MD5, SHA-1, or PBKDF2](https://stytch.com/docs/api/password-migrate)), scrypt is the Stytch-preferred algorithm. Whenever a user logs in, Stytch will verify their password hash using the algorithm it is currently stored with, and then rehash their password using scrypt and discard the old hash. Password rehashing is a common technique used to upgrade security as hashing algorithms evolve. | ||
|
|
@@ -215,7 +215,7 @@ The last lines of the object show the hash and salt that the script added from t | |
|
|
||
| ## Importing Users | ||
|
|
||
| First install a FusionAth plugin to handle the Stytch password hash algorithm, then import the users, and finally verify the import. | ||
| First install a FusionAuth plugin to handle the Stytch password hash algorithm, then import the users, and finally verify the import. | ||
|
|
||
| ### Build The Scrypt Password Hash Plugin For FusionAuth | ||
|
|
||
|
|
@@ -273,13 +273,13 @@ If you are not already running FusionAuth or want to test this process on anothe | |
| cd stytch/fusionAuthDockerFiles | ||
| docker compose up | ||
| ``` | ||
| - FusionAuth will now be running and browsable at `http://localhost:9011`. You can log in with `[email protected]` and `password`. The container is called `fa`. | ||
| - FusionAuth will now be running and browseable at `http://localhost:9011`. You can log in with `[email protected]` and `password`. The container is called `fa`. | ||
| - Open a terminal in the `fusionauth-contrib` root directory, where you built the plugin. Run the commands below to copy the JAR file into the FusionAuth container `plugins` directory. | ||
| ```sh | ||
| docker exec fa mkdir /usr/local/fusionauth/plugins | ||
| docker cp "Password Hashing Plugins/target/fusionauth-example-password-encryptor-0.1.0.jar" fa:/usr/local/fusionauth/plugins/fusionauth-example-password-encryptor-0.1.0.jar | ||
| ``` | ||
| - Finally, restart FusionAuth for it to detect the plugin. In the terminal where FusionAuth is running in Docker, press Ctrl + C to stop it, wait, and run `docker compose up` again. | ||
| - Finally, restart FusionAuth for it to detect the plugin. In the terminal where FusionAuth is running in Docker, press `control-C` to stop it, wait, and run `docker compose up` again. | ||
| ### Save The User Details And Hash To FusionAuth | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -146,10 +146,12 @@ WordPress has two tables related to users: `wp_users` and `wp_usermeta`. | |
|
|
||
| In `wp_users`, you will have data similar to the example below. This table holds identifiers and a password hash for each user. | ||
|
|
||
| ID|user_login|user_pass |user_nicename|user_email |user_url |user_registered |user_activation_key |user_status|display_name| | ||
| ---|----------|----------------------------------|-------------|----------------|----------------|-----------------------|---------------------------------------------|-----------|------------ | ||
| 1|user |\$P$BVrdsW/NUuXDi0Od0uUdk2SnJHHmQ01|user |user@example.com|http://127.0.0.1|2024-02-21 07:09:20.000| | 0|user | | ||
| 2|richard |\$P$B/kCzTMDV7ccClaRShJPz8suWQdKc5/|richard |richard@example.com | |2024-02-21 10:52:53.000|1708512773:\$P$BYELgLl.oz9lv.YRNp7ppBA1GxzOEY0| 0|a | | ||
| ``` | ||
| ID |user_login|user_pass |user_nicename|user_email |user_url |user_registered |user_activation_key |user_status|display_name| | ||
| ---|----------|----------------------------------|-------------|----------------------|----------------|------------------------|----------------------------------------------|-----------|------------ | ||
| 1 |user |$P$BVrdsW/NUuXDi0Od0uUdk2SnJHHmQ01|user |[email protected]| http://127.0.0.1 |2024-02-21 07:09:20.000 | | 0|user | | ||
| 2 |richard |$P$B/kCzTMDV7ccClaRShJPz8suWQdKc5/|richard |[email protected] | |2024-02-21 10:52:53.000 |1708512773:\$P$BYELgLl.oz9lv.YRNp7ppBA1GxzOEY0| 0|a | | ||
| ``` | ||
|
|
||
| Unfortunately, neither the [WordPress Codex](https://codex.wordpress.org/Database_Description) nor the [WordPress Developer Handbook](https://developer.wordpress.org) gives definitions of the database fields and their meanings. To be certain of their purpose, you would need to read the WordPress source code, but the column definitions below seem obvious enough to trust. | ||
|
|
||
|
|
||