Authorize sits at pending URGENT

[stephen1]

All of a sudden in the past 2 days I started getting auth0 to hang at pending on authorize. If I check the logs I can see that an account was successfully created, but for some reason this is happening despite any code changes. This is urgent as we were about to release our product. There have been no issues with our authentication for months/ nothing has been changed.

(Also want to add that this happens basically every other time I signup)

[stephen1]

I am also getting the following warning:

backend.js:6 Following parameters are not allowed on the /authorize endpoint: [user_metadata]

However this states you can pass metadata:

Can you pass user_metadata in a call to Auth0.js signupAndLogin method?

We are converting from using Lock to using a custom login with the Auth0.js Web SDK. With Lock, we’ve defined several custom fields (first name, last name, etc) that are mandatory for sign up. Is it possible to create the user’s account and pass in custom fields (via user_metadata) in one single call? The signupAndLogin method only seems to take username/password, and I’d have to make a subsequent call to update the user’s profile, which would be tricky with a redirect in between.

And here is my signup function:

  const signUp = async (email, password, prepaid, discount) => {
    await new Promise(function (resolve, reject) {
      auth0Client.redirect.signupAndLogin({
        "connection": 'Username-Password-Authentication',
        "email": email,
        "password": password,
        "user_metadata": {"prepaid": `${prepaid}`, "discount": `${discount}`}
      }, (err) => {
        if (err) {
          if (err.code === "user_exists" || err.code === "username_exists") {
            setAuthError(["That name is already in our system. Login or try again?"])
          } else if (
            err.code === "password_dictionary_error" || err.code === "password_no_user_info_error"
          ) {
            setAuthError(["That password might be too easy to guess.", "Try something that's not a common word"])
          } else if (
            err.code === "password_strength_error"
          ) {
            setAuthError(["That password might be too easy to guess.", "(Did you include a number, capital letter and special character?)"])
          }
          else {
            console.log('Something went wrong: ' + err.code)
            setAuthError(["Hmm, that doesn't look right. Please try again."])
          }
          return reject(new Error(err.code))
        }
        else {
          setUser(getUser());
          setAuthenticated(true);
          console.log("finished sign up")
        }
      })
    });
  }

[divyasmehta]

Were you able to find any solution? @stephen1
I am facing this same issue.

[divyasmehta]

@James.Morrison Hi James, Can you please help us with this?

[James.Morrison]

Good morning @divyasmehta and @stephen1

I apologize this wasn’t seen sooner. When you get a chance can you please snag me a HAR file capture of your login procedure which shows the challenge of where it hangs and then direct message it over to me along with your tenant name? I want to take a deeper look at what going on here. Thanks in advance!

Generate and Analyze HAR Files

[stephen1]

@James.Morrison

I apologize this wasn’t seen sooner. When you get a chance can you please snag me a HAR file capture of your login procedure which shows the challenge of where it hangs and then direct message it over to me along with your tenant name? I want to take a deeper look at what going on here. Thanks in advance!

Great thanks. I will send that over. I am still facing the issue and it’s now becoming a huge impediment to development.

[James.Morrison]

Issue appears resolved from discussions in DM. No changes were made. We will keep this topic open for another two weeks just in case the challenge reoccurs. Thanks!