similar to: How to expire HTTP basic authenticated session?

Hi, I used code from http://railscasts.com/episodes/82-http-basic-authentication but added it to Application controller to apply to the whole application class ApplicationController < ActionController::Base protect_from_forgery before_filter :authenticate protected def authenticate puts ''authenticating.. '' authenticate_or_request_with_http_basic do |username,

Hi all, I have an app that originally only supported form-based authentication, and showed pared-down content to unauthenticated users. I then layered on HTTP Basic authentication using authenticate_with_http_basic, which worked fine for scripts like LWP/ wget/curl. However, some web browsers refuse to submit credentials in the URL (eg.

Hi all, I want to implement tagging for my resources, but I found lots "acts_as_taggable" available: "acts_as_tabble", "acts_as_taggable_on", "acts_as_taggable_on_steroid", etc. Some of them are not in active development, and I do not know which one is more popular. So, any suggestions? Thanks in advance! Difei. -- Posted via http://www.ruby-forum.com/.

I can''t understand why authenticate_or_request_with_http_basic keeps failing even though I am entering the correct info. If I try to access /admin/items/new, I enter the correct info but I keep getting prompted. The strange part is that when I cancel out, I get "HTTP Basic: Acce". Here''s the controllers: class Admin::BaseController < ApplicationController

I just started using authenticate_or_request_with_http_basic. Is anyone working on the digest version of that? (I realize it may get a little complicated with the handshaking) If not, I wouldn''t mind contributing it. (I''ve implemented it in the past for other servers) -brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

Greetings all, I am wondering are there any thing like link_to_remote(:update, :url) in rails which preserves the navigation feature (back & forward button as well as bookmarks) of the browser? Thanks very much! Cheers, Difei -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

Hi, i''ve found some questions on the rails blog which haven''t any answer. Because i''m interested too i paste them here: # gonzo on 07 Dec 22:10: Does CSRF protection work with forms that are fully cached? # rugal on 08 Dec 20:14: Great job guys! Just an information about migrations. will t.timestamps create both created_at and updated_at? And for _on ?

hi all how to expire session in memcache session_store regards -- Posted via http://www.ruby-forum.com/.

Aki-san, Thanks for your feedback. Whatever ways will do. For instance, in a thunderbird mail client, a pop-up message or notification email telling client that the password will be expired in XX days, something like this, would be nice. Thanks, Masaharu Kawada On 2016?06?08? 15:49, Aki Tuomi wrote: > > On 08.06.2016 09:37, mkawada at redhat.com wrote: >> Dear list, >>

Dear list, Is it possible to give a notification about password exprire warning to users authenticated by OpenLDAP when the users login via dovecot using IMAP or POP? For example, when you ssh to a server and/or run ldapsearch, you can be warned with password expire warning like below: # ssh testuser at localhost testuser at localhost's password: Your password will expire in 31 minute(s).

Hi, i need to access a url www.sometesturl3456.com/index.php It prompts HTTP Authentication window asking username and password. I have do automatic HTTP Basic authentication without manual entry of username and password, as i am reading the content of page in ruby in rails using: response = open("www.sometesturl3456.com/index.php").read Please help me to know how this can be done.

Hi all, I have a problem with expiring sessions in the case with using mem_cache_store. I''ve been using ActiveRecord session store till now and expired them with SQL query. Yesterday I switched to memcache for storing sessions, however I can''t set an expireation period. My current config is this: ======================== memcache_options = { :c_threshold => 10_000,

hi, I''ve got an api which is using authenticate_or_request_with_http_basic What are you guys using to test this? I''m using rspec, and before I was using rspec-rails, I was using authorize from Rack::Test to do the authentication. However, authorize clearly doesn''t work when using rspec-rails, so I''m wondering what everyone else is doing? -- You received this

The example doesn''t work as described for me; not sure if I haven''t followed it right, or there''s a problem with the code. Can someone help me to determine what the problem is. Specifically, after adding the authentication code to the PostsController, with this line: before_filter :authenticate, :except => [:index, :show] The guide says that "we want the user

Hello, this is killing me: i can''t find a way to let idle sessions expire after a certain period of time. If they don''t expire, they will pile up until there''s no more memory available. Please, can anybody give me a hint? Basically, all I need is a hash or list with all the sessions in DRbStore. Greetings Michael Kastner

Hi folks, when I run expire-tool, I often see messages like the following: # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool Info: user/Trash: stop, expire time in future: Fri May 22 17:42:23 2009 the server's dovecot.conf contains the following line: expire = Trash 2 Junk 7 */News 30 */Reports 7 >From what I observe, an error of "expire time in future" in one

Expire plugin / expire-tool seems annoyingly inflexible currently, so I was thinking about a more generic redesign: The expire plugin keeps track of the oldest message in configured mailboxes. Its only configuration is the list of tracked mailboxes. There's no configuration like what the expire timeouts are or anything. There will be a new doveadm command: doveadm expunge [-u user | -A]

Hi! Here is the problem: passdb: daniell:*::::::user=daniell2 userdb: daniell2::uid:gid:gecos:home:: dovecot.conf: plugin { expire = SA.* 1 # (There are SA.HAM and SA.SPAM directories) } When copying a message to eg. the SA.HAM directory, then dovecot inserts this into my expires table: dovecot=# select * from expires ; username | mailbox | expire_stamp

Hi, I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled. I've had this in place for some time but until now never actually ran the expire-tool. I'm now trying to put this to use. The expire plugin as such is working fine and also the tool is working fine - up to a point. When I run it with --test it goes through a bunch of boxes and lists the messages it

Hello list, My dovecot setup have expire plugin enabled. It is working fine: new records added to database(sqlite), expire-tool successfully expunges old mail, but when expire-tool try to update database record for processed user, I get error in logs: root at mail dovecot 0:0 # /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh --test Info: koshikov.n at domain.com/Spam: