Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Setting force_ssl_login breaks overlay on non SSL Sites #3691

Closed
heisenbol opened this issue Jan 19, 2013 · 9 comments
Closed

Setting force_ssl_login breaks overlay on non SSL Sites #3691

heisenbol opened this issue Jan 19, 2013 · 9 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone
Long term

Comments

@heisenbol
Copy link

I'm using the force_ssl_login option to force the login screen to use SSL. Now I want to use the new overlay feature and am confronted with a message that "The Page Overlay session couldn't be launched yet."

From the faq I see that this happens because piwik uses SSL and the overlayed site does not support it. I tried to change the URL in my browser from https://mypiwikhost/xxxx to simple http, but this redirects again to the https version because of this force_ssl_login option. When I disable the force_ssl_login option, I see the overlay with no problems.

So the issue is that with the force_ssl_login option I can't use the overlay function on non SSL Sites. It seems that not only the login screen but all the piwik actions are redirected to SSL.

Keywords: overlay force_ssl_login
@mattab
Copy link
Member

mattab commented Jan 21, 2013

force_ssl_login should only redirect the login screen. are you sure you are using this config only? pls post your config.ini.php

@heisenbol
Copy link
Author

Attachment: Configuration file
config.ini.php

@heisenbol
Copy link
Author

Matt, thank you for taking time to respond to this ticket. I've created an attachment with my config.ini.php
I've replaced the stuff dealing with passwords.

@anonymous-matomo-user
Copy link

I've got the same behavior.
When i switch force_ssl_login=1 it will change the login page to HTTPS. So far it is right!
After successfull login it will not switch back to HTTP. Therefore the OverlayPage is trying to use HTTPS to the web page i'm tracking. But there is no HTTPS avialable.
Eather the OverlayPlugin uses HTTP or HTTPS as configurable parameter or a switch back to HTTP after login PIWIK will do the job.

My proposal is to save the compelete "URLs" like "http://myside.com" or when used HTTPS then "https://myside.com" in the "configuration -> websides" configuration page.

The "OverlayPage" should use precise this URL. So it is possible to use HTTP or HTTPS in the OverlayPage URL in the way the web side is accessable without dependence of accessing the PIWIK web side.

Best regards!

@diosmosis
Copy link
Member

In a7c4cf9: Refs #3691, refactor Goals 'conversions by type of visit' template/logic into reusable View in CoreHome.

Notes:

  • Removed need for initial AJAX loading in new view.

@diosmosis
Copy link
Member

Wrong ticket, a7c4cf9 refs #3619.

@mattab
Copy link
Member

mattab commented Jan 10, 2014

I dont actually see as a bug that we stay on SSL...

@heisenbol
Copy link
Author

well, then I would characterize the force_ssl_login option at least as "unclear" in what it does. I would expect that it just forces the login screen to be in a ssl connection, whereas

  1. it forces all access to piwik to be in SSL, and not only the login screen (what would be the difference with force_ssl??)
  2. it brakes features of piwik's web interface for non SSL sites.

This should be worth at least a comment or explanation in the documentation

@mattab
Copy link
Member

mattab commented Jan 13, 2014

Actually there is already a bug report which I just found: #4001

@heisenbol heisenbol added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
@mattab mattab mentioned this issue Jun 18, 2013
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Milestone
Long term
Development

No branches or pull requests
4 participants
@diosmosis @mattab @heisenbol @anonymous-matomo-user