We just upgraded our YouTrack instance from 4.0.2 up to 4.2.1 and I'm noticing some issues with a tool I've written to interop with the REST API.
Previously I was caching my Auth cookie/credentials in a naive way ( just caching for 2 hours actually ) without checking the Expiration time on the cookie header, however this didn't actually pose any problems and my app worked fine.
Under 2.4.1 however, I see that the cookie expires pretty much instantly:
curl -v -d login=markd http://youtrack/rest/user/login
Wed 10 Apr 2013 10:22:41 NZST
< Set-Cookie: JSESSIONID=...;Path=/
< Set-Cookie: jetbrains.charisma.main.security.PRINCIPAL=....;Path=/;Expires=Wed, 09-Apr-2014 22:22:41 GMT
Essentially this means I need to auth on every request? Doesn't this make using a cookie for auth kinda pointless?
Or has the API changed?