Hobo does not use basic HTTP authentication, it uses sessions. In the default setup, these are implemented via cookies.
If you look at the standard login form, it has these parameters: page_path authenticity_token login password remember_me page_path is only used if the login fails authenticity_token is used by the CSRF protection. For now, turn off CSRF protection: http://stackoverflow.com/questions/138311/how-do-i-turn-off-csrf-protection-in-a-rails-app/138372 Post the other parameters url encoded in the POST body. When successful, the page returned will contain a cookie called _my_app_session (if your app is named My App). Send this cookie with every subsequent request, and you should be fine. cheers, Bryan On Jun 12, 4:48 pm, Johannes Vanderknyff <[email protected]> wrote: > Folks, > > I am trying to get a rest client to authenticate to a hobo > application. I've tried to authenticate, but am having trouble. > > I've tried doing a "post" to /login, with header of "login" and > "password" but that comes back with an html page saying invalid > username and password. > I think I need to modify the hobo login process to be able to handle > "basic http authentication"... > > Anyone done this before? > > Thanks, > Johannes --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
