FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    HTTP 403 Forbidden Error Encountered When Login Attempted from http://we.dev.localtest.me:4211

    Scheduled Pinned Locked Moved Unsolved
    Q&A
    1
    1
    3.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tiksn
      last edited by

      What happened?

      Summary

      When attempting to log in from my application hosted on http://we.dev.localtest.me:4211/, an HTTP 403 Forbidden error is encountered. However, the redirection from http://localhost:4211/ works as expected.

      Caveat
      we.dev.localtest.me resolves to 127.0.0.1. localtest.me is a special domain that resolves to A=127.0.0.1 and AAAA = ::1. It is a convenient way to test a multi-tenant application locally.

      Steps to Reproduce: (My Local Setup)

      1. Create tenant
      2. Create an application for that tenant.
      3. Configure Authorized origins and Authorized redirects to contain http://localhost:4211 and http://we.dev.localtest.me:4211 (4211 is a port that UI is hosted on)
      4. Navigate to http://localhost:4211 and click login.
      5. It redirects to http://localhost:9011/ (FusionAuth also running in docker).
      6. Type the email and password from one of the users.
      7. Redirects back to http://localhost:4211.
      8. Navigate to http://we.dev.localtest.me:4211 and click login.
      9. It redirects to http://localhost:9011/ with status code 403 Forbidden.

      Expected Result:

      Login from http://we.dev.localtest.me:4211 should work identically to http://localhost:4211.

      Actual Result:

      FusionAuth fails to redirect back to http://we.dev.localtest.me:4211. It results in HTTP 403.

      Additional Information:

      • Environment: Development
      • Version: 1.53.2
      • My Repo - fossa-app/scripts

      Proposed Solution:

      Environment variable that allows insecure redirects (redirect to HTTP instead of HTTPS only)

      Notes

      Nothing is logged in docker console during the HTTP 403 error.

      Version

      1.53.2

      Affects Versions

      No response

      Note: This is a cross reference of an issue that I reported in GitHub github.com/FusionAuth/fusionauth-issues/issues/2876

      1 Reply Last reply Reply Quote 0
      • First post
        Last post