New RisePlayer App for Chrome does not take logins from webpages into account

  • 1
  • Problem
  • Updated 3 years ago
  • In Progress
Hi,

So today we encountered two problems when updating: first chromium (i know that is not offical chrome but it is a Raspberry Pi 2) and then the RisePlayer App.

As those are two seperate problems here the RisePlayer App update problem.
We updated to version 1.24.32 and suddenly it does not remember any logins which are made in other windows of the chrome. It even seems to be more restrictive with shortcuts as previously I was able to do a ctrl+n or t when interacting with the RisePlayer extension.
So as this is a ntlm login site we want to show via the player we only get a login denied page.

But with the previous version we were able to first login via a normal chromium page and then start the RisePlayer App. Then it got the login details from the already opened chromium session.

Was this change made by intention and is there another way to go around that problem?
Photo of Sanjit R

Sanjit R

  • 70 Points

Posted 3 years ago

  • 1
Photo of Alex Kolenoff

Alex Kolenoff

  • 3,506 Points 3k badge 2x thumb
Hi Sanjit,

I just wanted to follow up.  Were you able to find a resolution or workaround to this issue?  I don't think this was an intentional change on Rise's part.
Photo of Sanjit Roopra

Sanjit Roopra

  • 162 Points 100 badge 2x thumb
Hi Alex,

Nope now we had the problem with the new Rise Vision extension that it did not start anymore.
Which should be fixed with the latest version. But we installed the latest and now it is crashing at start-up.
I am not sure how to get logs from such a crash. But actually I think we are giving up on the RPI solution as it is too unstable.
I think we will go for a real Ubuntu system as a VM and the RPI only as a thin client displaying the content of the VM where Rise Vision will be running.
Photo of Alex Kolenoff

Alex Kolenoff

  • 3,506 Points 3k badge 2x thumb
Hi Sanjit, if the Pi was crashing in the last couple of days it may have been because of a much older Chrome version.  We just deployed a player version to try and deal with that situation but the symptoms sounds slightly different (white screen is what we have seen reported).    

The decision to move to Ubuntu sounds good.