tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/61-per-subdomain-cookiesLighthouse: Discussion 2011-04-07T05:34:26Ztag:help.lighthouseapp.com,2008-09-20:Comment/113462008-01-11T02:12:41Z2009-06-20T20:56:09ZPer subdomain cookies<div><p>It's written the way it is so you can use the same user profile
globally. This is to keep you from registering multiple accounts (I
probably have 20 various basecamp/campfire accounts). Though, I
really dig how 37s is using <a href=
"http://www.37signals.com/svn/posts/479-basecamp-gets-openid-and-open-bar">
OpenBar</a> to let people roam accounts.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/113462008-01-13T21:48:36Z2009-06-20T20:56:09ZPer subdomain cookies<div><p>ya ok - that makes sense - but i have to maintain multiple
identities</p>
<p>what about persistent logins, and if you have more than one
session, auth with that?</p>
<p>openid? -M</p></div>macktag:help.lighthouseapp.com,2008-09-20:Comment/113462008-04-19T22:21:54Z2009-06-20T20:56:15ZPer subdomain cookies<div><p>This has become an impediment for me as well now that Rails has
moved to Lighthouse. In theory having one login is nice, but in
practice it sort of breaks down. I don't necessarily want any of
the account information to be the same across projects. Title in
particular is problematic since it's almost guaranteed to be
different for every project. But in my case even email fails
because I have one email for my main job since it is of highest
priority and another email for personal and open source uses.</p>
<p>So in order to contribute to Rails now I have to use a secondary
browser.</p>
<p>I'd be quite happy to have one set of login credentials with
different account details for each lighthouse subdomain, but I know
that probably doesn't make sense from an engineering perspective.
Per-domain cookies seems an easy and sane approach. I know what you
have now currently makes things marginally easier for you, but it
makes my scenario (conservatively) 10 times worse than it makes
yours easier. If I was starting my own company I would likely avoid
Lighthouse for this very reason, superficial and inconsequential
though it may seem to those who use only their real name and a
single email address for everything.</p></div>Gabe da Silveiratag:help.lighthouseapp.com,2008-09-20:Comment/113462008-04-20T16:08:56Z2009-06-20T20:56:15ZPer subdomain cookies<div><p>We almost switched to per-domain logins, but Github works the
same way really. It'd also be a major architectural change to
Lighthouse that I'm not sure everyone wants. Once it's made, I
won't be able to go back easily.<br></p>
<p>I'd say that it being "10 times worse" is overly dramatic, but I
see where you're coming from. Thanks for the feedback.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/113462008-04-21T18:15:24Z2009-06-20T20:56:15ZPer subdomain cookies<div><p>I have many Basecamp accounts as well, and so I can see the
benefit of being logged in to all of them automatically. But in
practice, I just check "stay logged in" and I end up with a minor
annoyance (my password manager has the passwords anyway). However
with Lighthouse I have to remember to logout or I face a situation
where I post tickets from the wrong account, thus polluting my work
email and spreading private profile information around. Ignoring
that pitfall, if I want to use one browser for everything I am
forced to logout and login several times a day, easily 10 times as
much as I log into various basecamp accounts. So honestly 10x is
not hyperbole at all.</p>
<p>I don't think Github really provides a valid analogy here, since
the nature of git repositories is that they are easily cloned and
merged, and the purpose of github is to provide a central location
for many repositories to live and interact. This is different from
lighthouse where projects live in isolation and people have
different roles (everyone is a developer in git).</p>
<p>I think a quote from the <a href=
"http://git.or.cz/course/svn.html#know">Git-SVN crash course</a> is
appropriate here:</p>
<p>bq. Git can produce colorful output with some commands; since
some people hate colors way more than the rest likes them, by
default the colors are turned off</p>
<p>I think it ought to be possible to design some kind of cookie
hierarchy and preference system that allows people like you to have
your cake, and people like me to eat it too.</p></div>Gabe da Silveiratag:help.lighthouseapp.com,2008-09-20:Comment/113462008-04-22T20:51:51Z2009-06-20T20:56:15ZPer subdomain cookies<div><p>I wish it was as simple as a preference to turn off colors.
People have separate github accounts for private repositories too
and it's not a problem.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/113462008-05-01T01:35:25Z2009-06-20T20:56:16ZPer subdomain cookies<div><p>dasil: i've been thinking about this for awhile and talking to
others that have similar issues. Here are my thoughts:</p>
<ul>
<li>Move back to per-domain cookies again</li>
<li>Have some domain selector listing your various accounts, with
tokens to log you in quickly.</li>
<li>Optionally let it set a wildcard domain cookie if you do only
have one profile.</li>
<li>Allow per-account overrides for email and job title.</li>
<li>Add user profile merging.</li>
</ul></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/113462008-06-16T22:12:00Z2009-06-20T20:01:19ZPer subdomain cookies<div><p>I run multiple companies and am often also granted access to
other people's systems. Thus, I have at least 4 basecamp accounts,
and will probably have a lot more in the future. I expect
Lighthouse will eventually be similar... I have 2 accounts now, but
will likely need more in the future.</p>
<p>I like the way Basecamp handles this situation. If you have
multiple Basecamp accounts but enter the same OpenID url for each,
you get a dropdown list in the upper-left corner that lets you
switch between your accounts. Super easy (for the user).</p>
<p>Thus, I was extremely excited when Lighthouse got OpenID. I
thought it was designed to handle this situation. Initially, it
allowed me to set the same OpenID url on my two accounts, so I did.
Hilarity ensued, followed by frustration. At some point it stopped
allowing that, and now I can't save my profile anymore (I get
"Openid url has already been taken").</p>
<p>Thoughts?</p></div>anambatag:help.lighthouseapp.com,2008-09-20:Comment/113462008-06-29T15:30:33Z2009-06-20T20:01:20ZPer subdomain cookies<div><p>I would LOVE to have an "account switcher" to pop between
accounts easily. Rick, those changes sound good.</p></div>Kiere El-Shafie