Oops... clientSecret is not defined

Get Help
,
1

Hello everyone,

I was ramping up on the quickstart, did the following:

  • New application
  • Login flow creates a web3 wallet
  • Got my domain and client ID
  • Got my audience from API
  • Downloaded the quickrun zip file and opened on vs code
  • Modified auth_config.json with the requested info
  • npm i + npm start
  • Project runs fine

The issue however is clicking login. Auth0 errors out with “Oops… clientSecret is not defined”

even if I add clientSecret to the providerConfig within index.js that is surrounded by Auth0Provider I get this error.

No console errors, no network errors and no server-side errors.

Any help would be appreciated!

3

Hey @Emilio welcome to the community!

Hmm that’s odd! Do you mind sharing the quick start you are referring to?

4

Absolutely. It will most likely result in a 404- but when you do the quickstart you have the option to clone the github repo or download a zip file. I downloaded the zip file.

https://auth0.com/c25aaaaa-1fc3-42ca-a2e8-4e3915ff9b81

5

The name of the modal is: " You are downloading a working sample configured for the application Crossmint Auth Test"

If you need further info I can provide my clientId or domain. This is a test project so not concerned with key management here.

6

Also - using the Crossmint integration (I am part of the engineering team there) ; when I remove it the flow works fine. When I add Crossmint to the login flow it breaks with that error.

7

Hey @Emilio thanks for the additional info! FWIW, I’m getting the same error when adding this integration to an existing SPA application of mine :thinking: Same deal, all other login flows work.

I’m seeing this error in my logs (Auth0 Dashboard → Monitoring → Logs):

"action_name": "Create a Web3 wallet v1",
  "response": {
    "error": {
      "message": "clientSecret is not defined",
      "name": "ReferenceError",
      "stack": "ReferenceError: clientSecret is not defined\n    at exports.onExecutePostLogin (/data/io/node16/29f824a3-c713-46b6-8339-1e0ae948d6d2/webtask.js:9:3)\n    at /data/io/9fab410137a5d19440599fa605899088f984d674.js:7:907\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)"
    },
8

@tyf – I believe at this point it is action specific…

Is this an issue I should raise with my engineering team or is this potentially a bug your team needs to squash?

Thanks for testing, I appreciate it!

9

No problem, happy to help where I can! I’m not positive if this is something that needs to be addressed on your end or Auth0’s, but I’ve filed something internally just in case - I will certainly update you when I have more information myself :slight_smile:

11

Appreciate you, thanks!

1 Like
12

Hey @tyf

This ended up being an issue with our activation code – the wrong variable was introduced when we refactored. We are communicating the changes with your team to get the correct one up!

1 Like
13

Hey @Emilio - Gotcha! Thanks for letting us know :slight_smile:

14

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