Bug? meteor.userId on client is not equal to meteor.userId in method call SOLVED:different hostnames


#1

Hi all,

is this a bug? meteor.userId on client is not equal to meteor.userId in method call

mmm further analys shows that meteor.userID on both client and server are the same. But if I look in mongol I see a different user… any idea?

greetings


#2

You sure you are not viewing someone else’s account? Is insecure on?


#3

Well it is very strange… I use the same browser. But I open a new tab, and in here there is an iframe trying to get meteor.userid

Could it be the tabs in chrome have different meteor users logged in?


#4

insecure is not on.

Could it be something with 2 meteor servers running on 2 different ports?
Meteor on port 3000
Meteor on port 9000 (old style without ES6)

  1. I open meteor, login.
  2. click on a link which opens tab on separate meteor:9000
  3. this new tab contains an iframe which to external app, which redirects back to meteor:3000 (I implement single sign on, I use the logged in meteor:3000 user)
I see what is going on. I redirect back to my machine name in stead of localhost, and apparently that is a different domain name and as such I have to login again... versus