New Topic

Community Topic Question System Configuration

Chris McCarthy

Yellowfin Support Team

Assigned

Category System Configuration

Product Version 9.0

Our Yellowfin instance redirects to 127.0.0.1:8080 on login after selecting the client organisation

Stephen Bentley shared this question ago

Completed

Hi,

Our Yellowfin instance redirects to 127.0.0.1:8080 on login after selecting the client organisation in the multi-tenant login page.

We have the External Instance Base URL set correctly, and we are testing in private browsing mode (no browser cache). The redirect seems to be made by some Yellowfin JavaScript running in the page.

We are running Yellowfin 9.8, and SAML SSO is configured and enabled (in fact, the problem started after we configured that). The problem happens on normal (non SSO) logins (we haven't had chance to test SSO logins yet).

When we manually edit the URL in the browser to insert the correct domain, then things proceed as normal.

The same question

Replies (1)

Chris McCarthy ●

Hi Stephen,

Thanks for contacting Yellowfin Support and I hope you're doing well.

Are you accessing Yellowfin via an IP or a domain name? If it's a domain, does using the IP address instead give the same result?

Secondly, are you using HTTPS to connect? There might be some connector strangeness that is causing the redirect.

If you have any custom javascript in your Yellowfin folder, something here might be running after login on the main Yellowfin page and sending you to the localhost.

Does this only happen in private browsing mode? If so, it certainly could be a caching issue which might be resolved with an upgrade to the latest version.

Apologies for the large number of questions, but there's several possible causes. Let me know.

Kind regards,

Chris

Reply URL

Stephen Bentley ●

Thanks for your reply!

We're accessing Yellowfin via a domain name (over https). I've just tried using the IP address (also over https) and that gets the exact same issue.

We have a nginx proxy sitting in front of Yellowfin. However, the bad redirect is coming from JavaScript in the page, so it's not our proxy config (nor could we fix it with proxy config).

We don't have any custom javascript in our Yellowfin folder, as our Yellowfin install is the stock install (nothing added).

It happens both in normal browsing mode and in private browsing mode.

By inspecting the network traffic, I've discovered that the web page is making a request to this URL:

https://hostname/PageRedirectionCleanupAjaxAction.i4;6a528cbb-be14-4361-a4b5-784a4ba83762=38d49b3b-4de8-4590-be56-80291afb55e6?REQUESTTOKEN=a20951ed-b632-4fdf-a3c0-57232d464b20

which returns this body as its response:

<?xml version="1.0" encoding="UTF-8" ?>

<yellowfin-error><error-code>NOTLOGGEDIN</error-code><redirect>/index_mi.jsp</redirect>

<absolute-redirect>http://127.0.0.1:8080/index_mi.jsp</absolute-redirect><errors>;

<error>

<key>error.logon.session.timeout</key>

<description>Your session has timed out - please logon again</description>

</error>

</errors></yellowfin-error>

(Note that https://hostname is our Yellowfin domain)

Note that despite this response saying <error-code>NOTLOGGEDIN</error-code>, the login always succeeds (once we change the domain back to what it should be).

You can see the http://127.0.0.1:8080 in absolute-redirect element. However, this could be a red herring as there are a lot of requests happening (most of which are GET requests for JavaScript files), but this does look very suspicious.

Any help much appreciated!

Best,

Stephen

URL

Stephen Bentley ●

If you could redact the host name from my reply above that would be appreciated!

We've managed to fix our issue by adding the following to /opt/yellowfin/appserver/conf/server.xml within the Connector element:

proxyName="<host>" proxyPort="443" scheme="https"

(where <host> should be replaced with your host name)

Thanks,

Stephen

URL

Chris McCarthy ●

Hi Stephen,

Many thanks for letting me know you've fixed the issue and how you fixed it!

I've removed the hostname from your reply.

I was going to suggest commenting out a section from the ROOT.xml located in Yellowfin\appserver\conf\Catalina\localhost

sameSiteCookies="none"

We found this was timing out freshly logged in sessions to client orgs in older versions of Yellowfin and subsequently this was removed in 9.11.0.3

I've attached both old and new ROOT.xml files for your records.

If you have any other questions on this topic, let me know. Otherwise I think we can call this case closed!

Files:

URL

Stephen Bentley ●

Hi Chris,

Thanks for your help with this. I'm happy for this to be marked as closed.

URL

Chris McCarthy ●

Hi Stephen,

No worries. Have a good weekend!

Kind regards,

Chris

URL

William Corlin ●

@Stephen Bently Thanks for the URL: https://hostname/PageRedirectionCleanupAjaxAction.i4;6a528cbb-be14-4361-a4b5-784a4ba83762=38d49b3b-4de8-4590-be56-80291afb55e6?REQUESTTOKEN=a20951ed-b632-4fdf-a3c0-57232d464b20 /free online games and your question.

URL