No "Back to app" button on Password-Reset-Success screen even though Application Login URI is filled out

I have tried searching everywhere for an answer to this. I am using the Universal login experience, I have not customized my reset-password screen, it’s using the default template. I have the Application Login URI filled out and saved for my application.
However when a user goes through the reset-password auth0 flow, the success screen still doesn’t display the “Back to my app” button that it should.

This seems to be working on my other Auth0 application and everything is filled out the same. My overall tenant settings Login URI is not filled out because I need to use different login URL’s for different applications.
How can I fix this so the button shows up?


2 Likes

HI @daniMayf,

Welcome to the Auth0 Community!

How are you sending the password reset emails? Is the user clicking the “Forgot Password?” link or are you using the Management API?

Thanks,

Mary Beth

Hi Mary Beth,

I’m using the Management API. This is what our code looks like:

import { ManagementClient } from "auth0";


const client = new ManagementClient({
  domain: Bun.env.AUTH0_DOMAIN,
  clientId: Bun.env.AUTH0_USER_MANAGEMENT_CLIENT_ID,
  clientSecret: Bun.env.AUTH0_USER_MANAGEMENT_CLIENT_SECRET,
});

const response = await client.tickets.changePassword({
      client_id: Bun.env.AUTH0_APP_CLIENT_ID,
      connection_id: Bun.env.AUTH0_USER_MANAGEMENT_CONNECTION_ID,
      email,
      mark_email_as_verified,
      includeEmailInRedirect: false,
    });
return response.data.ticket; // <-- we return the response.data.ticket to the client which redirects the user to the Auth0 reset password page

Hi @daniMayf,

Thanks for confirming! Does the affected application’s client_id in your tenant end in Bcoq? If so, I believe I see the issue. Looking at the raw response of that application, there’s a custom_login_page_preview property with a value set to an HTML page. You can use this endpoint to see that property: Get a Client by ID

Setting custom login pages enforces classic login and that button would not appear. I would recommend saving the object returned in the above endpoint as a backup, and then use the patch a client endpoint to remove the custom_login_page_preview property.

If this is the application affected, could you please give that a try? If this is not the application, can you provide me with the last four characters of the client_id? I did check all of the applications in the tenant and did not see any other application with the custom_login_page_preview property set.

Best,

Mary Beth

Hi @marybeth.hunter ,

Thanks for that information, however the client_id we’re using ends in JhmUC and I’m pretty sure we’re using the universal login for that Application

Hi @daniMayf,

Interesting!! Okay, let me take a closer look and I will get back to you as soon as I can!

Thanks,

Mary Beth

1 Like

Thanks for your help @marybeth.hunter !

1 Like

Hi @marybeth.hunter , this issue ended up being user error. There was an issue with the AUTH0_APP_CLIENT_ID key of our environment variable.

1 Like

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