Per subdomain cookies
Hi
I have two lighthouse accounts, would it be possible to set auth
cookies on each account at the subdomain level so that I could have
separate tabs with different accounts logged in?
account1.lighthouseapp.com and account2.lighthouseapp.com
should be different cookies
i'd like to be able to use both without switching login details
please!
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Rick on 11 Jan, 2008 02:12 AM
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 OpenBar to let people roam accounts.
2 Posted by mack on 13 Jan, 2008 09:48 PM
ya ok - that makes sense - but i have to maintain multiple identities
what about persistent logins, and if you have more than one session, auth with that?
openid? -M
3 Posted by Gabe da Silveir... on 19 Apr, 2008 10:21 PM
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.
So in order to contribute to Rails now I have to use a secondary browser.
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.
4 Posted by Rick on 20 Apr, 2008 04:08 PM
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.
I'd say that it being "10 times worse" is overly dramatic, but I see where you're coming from. Thanks for the feedback.
5 Posted by Gabe da Silveir... on 21 Apr, 2008 06:15 PM
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.
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).
I think a quote from the Git-SVN crash course is appropriate here:
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
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.
6 Posted by Rick on 22 Apr, 2008 08:51 PM
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.
7 Posted by Rick on 01 May, 2008 01:35 AM
dasil: i've been thinking about this for awhile and talking to others that have similar issues. Here are my thoughts:
8 Posted by anamba on 16 Jun, 2008 10:12 PM
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.
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).
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").
Thoughts?
9 Posted by Kiere El-Shafie on 29 Jun, 2008 03:30 PM
I would LOVE to have an "account switcher" to pop between accounts easily. Rick, those changes sound good.