From 3ebdd47737e89e930661ced8599c005f74ff760c Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Sun, 12 Aug 2018 15:02:38 -0500 Subject: [PATCH] doc/dev/cephx_protocol: drop auid reference Signed-off-by: Sage Weil --- doc/dev/cephx_protocol.rst | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/doc/dev/cephx_protocol.rst b/doc/dev/cephx_protocol.rst index bf4df30fd46..ad633c2229a 100644 --- a/doc/dev/cephx_protocol.rst +++ b/doc/dev/cephx_protocol.rst @@ -147,15 +147,17 @@ give it an authentication ticket. We fetch C's ``eauth`` structure. This contains an ID, a key, and a set of caps (capabilities). -The client sent us its old ticket in the message, if it had one. If so, we set a flag, -``should_enc_ticket``, to true and set the global ID to the global ID in that old ticket. -If the attempt to decode its old ticket fails (most probably because it didn't have one), -``should_enc_ticket`` remains false. Now we set up the new ticket, filling in timestamps, -the name of C, the global ID provided in the method call (unless there was an old ticket), and -his ``auid``, obtained from the ``eauth`` structure obtained above. We need a new session key -to help the client communicate securely with us, not using its permanent key. We set the -service ID to ``CEPH_ENTITY_TYPE_AUTH``, which will tell the client C what to do with the -message we send it. We build a cephx response header and call +The client sent us its old ticket in the message, if it had one. If +so, we set a flag, ``should_enc_ticket``, to true and set the global +ID to the global ID in that old ticket. If the attempt to decode its +old ticket fails (most probably because it didn't have one), +``should_enc_ticket`` remains false. Now we set up the new ticket, +filling in timestamps, the name of C, and the global ID provided in the +method call (unless there was an old ticket). We need a new session +key to help the client communicate securely with us, not using its +permanent key. We set the service ID to ``CEPH_ENTITY_TYPE_AUTH``, +which will tell the client C what to do with the message we send it. +We build a cephx response header and call ``cephx_build_service_ticket_reply()``. ``cephx_build_service_ticket_reply()`` is in ``auth/cephx/CephxProtocol.cc``. This -- 2.39.5