I am using this code for initialize my auth0 object in my login.html page // Initializing our Auth0Lock var lock = new Auth0Lock( ‘YOUR_CLIENT_ID’, ‘YOUR_DOMAIN’ auth: { params: { state: etc… etc… responseType: ‘code’, redirectUrl: ); is it dangerous to put this information in public acc…

Hello @soporte.desarrollo , Welcome to the Community! I would not openly publicise a client ID like that, at least not for a “real” service, but Client IDs should be treated as public information similar to a “username”. They are not a secret, but I wouldn’t leave them where they can be easily picke…

Is it dangerous to put my client_id in public js file using lock v11?

Get Help

system Closed November 17, 2020, 7:01am 8

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Is it okay to have auth0 client information accessible over a public API? Get Help auth0 , client , public	5	6995	March 2, 2018
Safe management of Auth0 information in source control Get Help api , spa	4	5149	August 28, 2019
@auth0/auth0-spa-js library, Custom Params, Scopes Get Help lock , auth0	1	3093	December 30, 2019
An error occurred when fetching client data for Lock: https:// Get Help nodejs , auth-lock	2	5099	December 25, 2018
When customizing the login screen using auth0.js, include information about available connections to client id Product Feedback connections , auth0js , login	1	2466	November 5, 2021

Is it dangerous to put my client_id in public js file using lock v11?

Related topics