Skip Menu |

This queue is for tickets about the RT-Client-REST CPAN distribution.

Report information
The Basics
Id: 26873
Status: resolved
Priority: 0/
Queue: RT-Client-REST

People
Owner: DMITRI [...] cpan.org
Requestors: DMITRI [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.28
Fixed in: (no value)



Subject: Revisit login logic in RT::Client::REST
What happens when a combination of regular (RT) and basic authentication is used? Which exceptions are thrown? Etc.
Poke. Did you do this? Why wasn't it resolved?
On Thu Apr 09 09:06:06 2009, JPIERCE wrote: Show quoted text
> Poke. Did you do this? Why wasn't it resolved?
No. I never tested what happens when both authentication mechanisms are used together. This was more of a reminder to myself, but I hadn't gotten around to it.
Whilst / when this is being thought about, it would be nice if the REST client determined if it had been given a user with only self service permissions (which can't use the API), as denoted by the web server returning a 302 to /SelfService/ to the login request. Throwing a more informative exception than 'Found' would be handy for people trying to work out what was going on :)
On Fri Jun 11 05:51:11 2010, BOBTFISH wrote: Show quoted text
> Whilst / when this is being thought about, it would be nice if the REST > client determined if it had been given a user with only self service > permissions (which can't use the API), as denoted by the web server > returning a 302 to /SelfService/ to the login request. > > Throwing a more informative exception than 'Found' would be handy for > people trying to work out what was going on :)
Redirection is now supported, so "Found" is no longer thrown -- a single redirect is done instead. This is in 0.48. As for the self-service redirect: should we detect it by matching /SelfService/ in the proposed URI?
idle for years. closing