Admin Console's "Back to the application" link returns the user to the Admin Console, so the account pages are a dead end #10848

3 Answer(s)

• 

  0

  AI-Bot created one month ago

  Support Team ABP Agent

  • With ABP Volo.Abp.AdminConsole 10.4.x–10.6.x (including 10.6.0), the Admin Console React UI renders “Back to the application” as a client-side router link to /. Since the Admin Console router is mounted with basepath = /admin-console, that navigation resolves to /admin-console, not to your separate React SPA. In other words: in these versions there is no built-in “return URL” concept for that link in the shipped Admin Console bundle.

  • The Admin Console runtime configuration endpoint (/admin-console/api/config) (as documented) exposes Admin Console options like enabling/disabling, redirecting / to /admin-console, authority/client id/scope, theme, localization, etc., but it does not document (or provide) an application.returnUrl that the built-in UI could use for this link. So there is nothing you can configure today (in 10.6.0) to make that link point back to your separate React app.

  • Practical, supportable workaround (backend-side) that avoids patching minified JS:

    1. Disable the “redirect backend root to admin-console” behavior so that / is not the Admin Console entry point:
       • Set AdminConsole:RedirectRootToAdminConsole to false (or the equivalent AbpAdminConsoleOptions.RedirectRootToAdminConsole = false).
    2. Then ensure your backend root / (or a dedicated endpoint like /return-to-app) performs an HTTP redirect to your SPA root (e.g. /app) — using your own controller/middleware.
       • This way, even if the Admin Console navigates to /admin-console (or to / under certain conditions), you can control what / does and make it “go back to the application”.

  • If you want the behavior you described (“application.returnUrl from runtime config + render as <a href=...>”), that matches the documented pattern in the “Non React UI Integration” document, but Admin Console does not currently implement that pattern in the shipped package versions you tested.

  Sources:

  • https://abp.io/docs/10.6/framework/ui/react/admin-console
  • https://abp.io/docs/10.6/framework/infrastructure/app-urls
  • https://abp.io/docs/latest/low-code/non-react-ui-integration

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  severances@gc.adventist.org created one month ago

  This is a bug report. Having a back to application link that is broken out of the box isn't ideal--especially if the fix involves altering minified code.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  Hi,

  You're right, this is a bug on our side.

  Until the fix ships, open the account pages from your SPA in a new tab, so closing the tab is the way back for the users you send there:

  <a
    href={`${backendUrl}/admin-console/account/manage`}
    target="_blank"
    rel="noopener noreferrer"
  >
    {t('AbpAccount::MyAccount')}
  </a>
  

  The next version fixes it the way you suggested — set the application url and those links become plain anchors to it:

  {
    "AdminConsole": {
      "ReturnUrl": "https://example.org/app"
    }
  }
  

  Your ticket has been refunded.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel