- 29 May, 2010 1 commit
-
-
Sage Weil authored
We were only requesting renewal after our tickets expire; do so before that. Most of the low-level logic for this was already there; just use it. Signed-off-by:
Sage Weil <sage@newdream.net>
-
- 17 May, 2010 1 commit
-
-
Sage Weil authored
Signed-off-by:
Sage Weil <sage@newdream.net>
-
- 10 Feb, 2010 1 commit
-
-
Sage Weil authored
Add infrastructure to allow the mon_client to periodically renew its auth credentials. Also add a messenger callback that will force such a renewal if a peer rejects our authenticator. Signed-off-by:
Yehuda Sadeh <yehuda@hq.newdream.net> Signed-off-by:
Sage Weil <sage@newdream.net>
-
- 18 Nov, 2009 1 commit
-
-
Sage Weil authored
When we open a monitor session, we send an initial AUTH message listing the auth protocols we support, our entity name, and (possibly) a previously assigned global_id. The monitor chooses a protocol and responds with an initial message. Initially implement AUTH_NONE, a dummy protocol that provides no security, but works within the new framework. It generates 'authorizers' that are used when connecting to (mds, osd) services that simply state our entity name and global_id. This is a wire protocol change. Signed-off-by:
Sage Weil <sage@newdream.net>
-