Lighthouse Users

Comments and changes to this ticket

• 

  Will August 6th, 2008 @ 10:29 AM

  • → Tag changed from “” to “@high api”
  • → State changed from “new” to “open”
  • → Assigned user changed from “” to “rick”
• 

  Peter Jaros August 27th, 2008 @ 11:22 AM

  Having the same issue at http://dropio.lighthouseapp.com/...>

• 

  rick September 3rd, 2008 @ 07:04 PM

  I can't duplicate this at all. I've verified that i can access /projects.xml without logging in (listing only public projects), with a token, and with the email/password.

• 

  Josh Clayton September 3rd, 2008 @ 07:10 PM

  I get this error by attempting to access a project with Lighthouse Keeper, if that helps at all.

• 

  rick September 3rd, 2008 @ 07:23 PM

  Yes, it only shows public projects in Lighthouse Keeper. It seems like it's sending the authentication info incorrectly. I'll have to work with Martin more closely on this.

• 

  Peter Jaros September 4th, 2008 @ 09:35 AM

  @rick:

  To be clear, this is not limited to Lighthouse Keeper. I can't access http://dropio.lighthouseapp.com/... using my (double- and triple-checked) email and password.

• 

  colin September 4th, 2008 @ 11:06 AM

  I'm the original user Martin was referring to. I think I might have discovered what is happening, at least in my case. Here's my scenario: - I created an account for myself (cgray@yousoftware) and created a project. - I then realized that I'd rather use my support email address for submitting bugs, so I created a second account (support@yousoftware) and gave it access to the project. - From that point on, I've always only used the support account.

  As Peter mentioned, this isn't really related to LHK. If I would curl the projects.xml file using the support credentials, it returns ""

  What I discovered today is (a) I could use my (forgotten) cgray credentials and it would work and then (b) when I changed the settings to give the support account administrator access (vs just access to the single project), curl returns the proper results for project.xml.

  So, long story short, in my case it appears the problem is that projects.xml will not return a result unless you are an administrator account. At some level this makes sense, but certainly breaks for the way Martin's LHK is trying to use it.

  Hopefully this information helps out others in this situation...

• 

  Martin Pilkington September 4th, 2008 @ 11:22 AM

  In which case this would be a bug Will found a while ago. I thought one of us filed a bug on it but I can't seem to find it.

• 

  Bob Parker September 5th, 2008 @ 12:57 PM

  I can confirm this as well (also emailed Martin about it regarding Lighthouse Keeper last night).

  Very interested in the resolution, as I am not an administrator, but do a LOT of maintenance on tickets in our application.

• 

  Will September 5th, 2008 @ 12:59 PM

  Its high on the priority list. Rick planned to get this wrapped up last weekend, but we already had a lot on the Lighthouse plate.

• 

  Arik Jones September 9th, 2008 @ 07:30 AM

  Confirmed using Lighthouse Keeper.

• 

  Arik Jones September 15th, 2008 @ 08:05 AM

  Any progress on this bug?

• 

  halbtuerke September 25th, 2008 @ 04:20 AM

  • → Tag changed from “@high api” to “"@high" api”

  I tried using Lighthouse Keeper on my Lighthouse account on which I am an administrator but still I cannot login.

  Is there any estimation on when this bug gets resolved?

  Thanks in advance

• 

  rick September 25th, 2008 @ 09:57 AM

  • → Tag changed from “"@high" api” to “"@high" api error”

  It's a problem with LHK calling the api incorrectly. It works great via curl. I've already talked to Martin about this.