Skip to content

Removing outdated Lock for Web#1316

Open
avanscoy wants to merge 1 commit into
mainfrom
fix/docs-lock-for-web-removal
Open

Removing outdated Lock for Web#1316
avanscoy wants to merge 1 commit into
mainfrom
fix/docs-lock-for-web-removal

Conversation

@avanscoy

@avanscoy avanscoy commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Description

Removing old Lock for Web articles.

References

Testing

Checklist

  • I've read and followed CONTRIBUTING.md.
  • I've tested the site build for this change locally.
  • I've made appropriate docs updates for any code or config changes.
  • I've coordinated with the Product Docs and/or Docs Management team about non-trivial changes.

@avanscoy avanscoy requested a review from a team as a code owner June 1, 2026 14:39
@avanscoy avanscoy added main-docs Changes related to auth0's main docs (https://auth0.com/docs) MERGE-ON-APPROVAL Approving reviewer should merge. labels Jun 1, 2026
@github-actions

github-actions Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Status Count
🔍 Total 698
✅ Successful 133
⏳ Timeouts 0
🔀 Redirected 24
👻 Excluded 534
❓ Unknown 0
🚫 Errors 7
⛔ Unsupported 0

Errors per input

Errors in main/docs/authenticate/identity-providers/social-identity-providers/reprompt-permissions.mdx

Errors in main/docs/get-started/tenant-settings.mdx

Errors in main/docs/libraries.mdx

Errors in main/docs/manage-users/user-migration/user-migration-scenarios.mdx

Redirects per input

Redirects in main/docs/authenticate/identity-providers/enterprise-identity-providers/adfs.mdx

Redirects in main/docs/authenticate/identity-providers/social-identity-providers/reprompt-permissions.mdx

Redirects in main/docs/authenticate/login/universal-vs-embedded-login.mdx

Redirects in main/docs/authenticate/passwordless/implement-login/embedded-login/spa.mdx

Redirects in main/docs/authenticate/single-sign-on.mdx

Redirects in main/docs/get-started/architecture-scenarios/b2e.mdx

Redirects in main/docs/get-started/architecture-scenarios/business-to-business/authentication.mdx

Redirects in main/docs/get-started/architecture-scenarios/business-to-business/launch/testing.mdx

Redirects in main/docs/get-started/architecture-scenarios/business-to-business/quality-assurance.mdx

Redirects in main/docs/get-started/architecture-scenarios/business-to-consumer/launch/testing.mdx

Redirects in main/docs/get-started/architecture-scenarios/business-to-consumer/quality-assurance.mdx

Redirects in main/docs/libraries.mdx

Redirects in main/docs/manage-users/user-accounts/metadata.mdx

Redirects in main/docs/manage-users/user-migration/user-migration-scenarios.mdx

@mintlify

mintlify Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
auth0 🟢 Ready View Preview Jun 1, 2026, 2:47 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@hazel-nut hazel-nut left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm again not sure that removing the links here is the right way to handle this change...

  • at a higher level, are we deprecating lock? is this a library that customers should still use? is there a replacement they should be using instead? (having a fuller PR description here to provide context on removing this content would help!)

  • regardless of the above answer, if we're removing all the core docs for the library, does it make sense to retain other content that explains how to use it?

there seemed to be other content errors here as well. i noted some of it inline but i do think this needs a bit more work before it's ready.

Comment on lines 15 to +23
## Universal Login + Lock (passwordless)

This method uses a custom login page with the **Lock (passwordless)** template, and authenticates user with the [Lock for Web SDK](/docs/libraries/lock):
This method uses a custom login page with the **Lock (passwordless)** template:

1. Go to [Dashboard > Branding > Universal Login](https://manage.auth0.com/#/login_settings) and click the **Login** tab.
2. Enable the **Custom Login Page** toggle, and select the **Lock (passwordless)** template. The HTML template will update with code using the Lock widget with Passwordless customization options.
3. Customize the template, and click **Save Changes**.

You can use HTML and CSS to customize the login form, and preview the changes within the Dashboard. To learn more about how to customize the **Lock (passwordless)** template, read the Passwordless section in [Lock for Web SDK](/docs/libraries/lock).
You can use HTML and CSS to customize the login form, and preview the changes within the Dashboard.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like this whole section is referring to lock.

Classic Login is an Auth0-hosted login experience that relies on JavaScript for customization. Implementing Classic Login is less complex than embedding the authentication process directly in your app, and it can help prevent the dangers of cross-origin authentication.

Classic Login is built on top of Auth0's JavaScript libraries ([Lock.js](/docs/libraries/lock), [auth0.js](/docs/libraries/auth0js), <Tooltip tip="Multi-factor authentication (MFA): User authentication process that uses a factor in addition to username and password such as a code via SMS." cta="View Glossary" href="/docs/glossary?term=MFA">MFA</Tooltip> Widget, and Password Reset). When customizing Classic Login pages in the <Tooltip tip="Auth0 Dashboard: Auth0's main product to configure your services." cta="View Glossary" href="/docs/glossary?term=Auth0+Dashboard">Auth0 Dashboard</Tooltip>, the default templates use the same JavaScript libraries to create a more natural transition between the default user interface and a custom one.
Classic Login is built on top of Auth0's JavaScript libraries (Lock.js, [auth0.js](/docs/libraries/auth0js), <Tooltip tip="Multi-factor authentication (MFA): User authentication process that uses a factor in addition to username and password such as a code via SMS." cta="View Glossary" href="/docs/glossary?term=MFA">MFA</Tooltip> Widget, and Password Reset). When customizing Classic Login pages in the <Tooltip tip="Auth0 Dashboard: Auth0's main product to configure your services." cta="View Glossary" href="/docs/glossary?term=Auth0+Dashboard">Auth0 Dashboard</Tooltip>, the default templates use the same JavaScript libraries to create a more natural transition between the default user interface and a custom one.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this sentence still mentions lock.js even with the link removed. is that what we want?



If you use [Auth0.js](/docs/libraries/auth0js) on the Universal Login page, you must set the `overrides` option.
If you use Auth0.js on the Universal Login page, you must set the `overrides` option.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why remove this link?

* **Enable Gravatar Integration:** When user enters their email, their associated Gravatar picture is displayed in the embedded Auth0 login form. Option name is `gravatar`.
* **Login Name Style:** Selecting **Email** will require users to enter their email address to login. Set this to **Username** if you do not want to force a username to be a valid email address. Option name is `username_style`. Option name is `client_secret_b64_encoded`.
* **Primary Color:** To learn more about this setting, read [Lock Configuration Options](/docs/libraries/lock/lock-configuration). Option name is `primary_color`.
* **Primary Color:** To learn more about this setting, read the Lock Configuration Options documentation. Option name is `primary_color`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this tells the user to read an article that doesn't exist and doesn't have a link

There are many options on the **Appearance** tab of the plugin settings page that can change the look and feel of the login form that is embedded on your site (`wp-login/php` page, shortcodes, or widgets). To learn more about these options, read [Configure Login by Auth0](/docs/customize/integrations/cms/wordpress-plugin/configure-login-by-auth0). This will not affect the the login form on the Auth0-hosted <Tooltip tip="Universal Login: Your application redirects to Universal Login, hosted on Auth0's Authorization Server, to verify a user's identity." cta="View Glossary" href="/docs/glossary?term=Universal+Login">Universal Login</Tooltip> Page.

There is also a field called "Extra Settings" on the **Advanced** tab that accepts a valid JSON object with all the settings you want to configure. This will override any changes made on the **Appearance** tab. To see all possible configuration options, read [Lock Configuration Options](/docs/libraries/lock/lock-configuration).
There is also a field called "Extra Settings" on the **Advanced** tab that accepts a valid JSON object with all the settings you want to configure. This will override any changes made on the **Appearance** tab. To see all possible configuration options, read the Lock Configuration Options documentation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this tells the user to read an article that doesn't exist and doesn't have a link

* Present users with only one or more specific login methods

To learn more about customizing the Lock widget, review the [Lock Configuration Options](/docs/libraries/lock/lock-configuration).
To learn more about customizing the Lock widget, review the Lock Configuration Options documentation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this tells the user to read an article that doesn't exist and doesn't have a link

Comment on lines 58 to +76
@@ -73,7 +73,7 @@ lock.getUserInfo(accessToken, function(error, profile) {



You can use `additionalSignUpFields` to add custom fields to user sign-up forms. When a user adds data in a custom field, Auth0 stores entered values in that user's `user_metadata`. To learn more about adding `user_metadata` on signup, read [Additional Signup Fields](/docs/libraries/lock/lock-configuration#additionalsignupfields).
You can use `additionalSignUpFields` to add custom fields to user sign-up forms. When a user adds data in a custom field, Auth0 stores entered values in that user's `user_metadata`. To learn more about adding `user_metadata` on signup, read the Additional Signup Fields documentation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this whole section still talks about using lock. should we still have this?

### Use Lock

You can customize the Lock UI to display links to your terms and conditions and/or privacy statement pages, and a consent checkbox that the user has to check in order to sign up. This can be done with the `mustAcceptTerm`s Lock option. This property, when set to `true`, displays a checkbox alongside the terms and conditions that must be checked before signing up. The terms and conditions can be specified using the languageDictionary option. To learn more, read [Lock Configuration Options](/docs/libraries/lock/lock-configuration).
You can customize the Lock UI to display links to your terms and conditions and/or privacy statement pages, and a consent checkbox that the user has to check in order to sign up. This can be done with the `mustAcceptTerm`s Lock option. This property, when set to `true`, displays a checkbox alongside the terms and conditions that must be checked before signing up. The terms and conditions can be specified using the languageDictionary option. To learn more, read the Lock Configuration Options documentation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tells the user to read docs that don't exist

2. Select the **Login** view, and enable the **Customize Login Page** toggle.
3. Locate the **Default Templates** dropdown, and select `Lock`. The code block will be pre-populated for you.
4. To add a field for the `consentGiven` metadata, use the `mustAcceptTerms` option. To include links to your Terms & Conditions and/or privacy policy pages, use the `languageDictionary` option. To learn more, read [Lock Configuration Options](/docs/libraries/lock/lock-configuration). The example below displays text that says `I agree to the terms of service and privacy policy` (including links to both pages) next to the flag:
4. To add a field for the `consentGiven` metadata, use the `mustAcceptTerms` option. To include links to your Terms & Conditions and/or privacy policy pages, use the `languageDictionary` option. To learn more, read the Lock Configuration Options documentation. The example below displays text that says `I agree to the terms of service and privacy policy` (including links to both pages) next to the flag:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tells the user to read docs that don't exist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

main-docs Changes related to auth0's main docs (https://auth0.com/docs) MERGE-ON-APPROVAL Approving reviewer should merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants