Description of problem: we've verified satellite logins do not work in elinks or lynx. this may be an issue for visually-impaired users. More Info: <zeus_hm> username and password get sent, but get redirected to relogin page <zeus_hm> it could be cookie related.
It was indeed a cookie issue as those two text browsers didn't like having a cookie that was set to expire so far in the future (~33 years). Fixed in rev 132983. Note that this will need to be tested extensively to make sure that the changes didn't cause breakage with the java perl interaction or logins in general. Also testing across browsers is a must! Also note that elinks can be used with any existing satellite by changing the cookie.max_age value to 0 (so that elinks ignores the cookies age completely). This will not be needed in 5.1 though.
unit test fixes in rev 132984.
Moving to ON_QA
verified in build 20
Also in rev 133153. I had to adjust how the cookie info was stored in the DB. Taskomatic was expecting the expire time in the DB to be the date of expiration, but we were just sticking the expire time.
Thanks, Cliff. Here's how it'll go into the notes: A bug that prevented the usage of text based web browsers to login and use &RHN; Satellite Server has been fixed.
release_pending
UI Enhancements for 5.1 Sat GA so Closed for Current Release.
*** Bug 324601 has been marked as a duplicate of this bug. ***