Pre-user-registration throw "Extensibility error"

Help
, ,
1

I have added “Domain Based Registration” action to the pre-user-registration trigger. And it is work fine but last time it is always throw the “Extensibility error” in the registration flow. All other without any customisation.

In the logs inside Auth0 dashboard I found an exception that looks like:

{
  "action_name": "Domain Based Registration v1",
  "response": {
    "error": {
      "message": "Cannot read properties of undefined (reading 'split')",
      "name": "TypeError",
      "stack": "TypeError: Cannot read properties of undefined (reading 'split')\n    at exports.onExecutePreUserRegistration (/data/io/node16/5357b479-0b08-40d2-85c6-29bb28e31743/webtask.js:5:46)\n    at /data/io/0b8f48245cde1e21775f8deb6eaea6698910fb0a.js:5:857\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)"
    },
    "stats": {
      "action_duration_ms": 3
    }
  },
  "started_at": "2024-11-08T10:44:07.562Z",
  "ended_at": "2024-11-08T10:44:07.584741188Z"
}

As I understand it is something inside the action that was developed by Auth0.
How can I fix that?

4

Hi @denaikG

Welcome to the Auth0 Community!

Can you share the content of the Domain-Based Registration Configuration Action with me via DM?

Thanks
Dawid

5

Hello. Yes, I can share it with you. But where I can do that? Can you write to me in DM?

7

I am facing the same problem.
Have you done it?

8

Hi @anhht,

Can you send me your account name and tenant name via DM? We are still investigating this issue.

Thanks
dawid

10

The problem is in the Domain Based Registration v1 code. I replaced it with the custom code for checking domains, and the error has not occurred.

1 Like
11

Yeah, I am totally agree with you. Can you share your custom code please?

12

Do you have an estimate for when it will be fixed?

13

Experiencing the same issue. The workaround is fine, but would love to understand more about the root cause and what the ETA for fixing the published DBR action is.

Thank you!

2 Likes
15

Looks like the issue was fixed on the Auth0 side. But it would be nice if they let us know about this…

16

Hi team,

After further investigation, we’ve identified the root cause of this bug, and the team fixed it. If you discover that this bug persists or reoccurs, please contact me as soon as possible.

Thanks!
Dawid

17

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