Generate a GUID for each successful authorization, this will allow the
tying of events in the logs back to a specific session.
Signed-off-by: Gary Lockyer <gary@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
[noprint] DATA_BLOB session_key;
[value(NULL), ignore] cli_credentials *credentials;
+
+ /*
+ * It is really handy to have our authorization code log a
+ * token that can be used to tie later requests togeather.
+ * We generate this in auth_generate_session_info()
+ */
+ GUID unique_session_token;
} auth_session_info;
typedef [public] struct {
return NT_STATUS_NO_MEMORY;
}
+ session_info->unique_session_token = GUID_random();
+
*session_info_out = session_info;
return NT_STATUS_OK;
}
return status;
}
+ session_info->unique_session_token = GUID_random();
+
*session_info_out = session_info;
return NT_STATUS_OK;
}
return status;
}
+ session_info->unique_session_token = GUID_random();
+
*session_info_out = talloc_move(mem_ctx, &session_info);
TALLOC_FREE(frame);
return NT_STATUS_OK;
return nt_status;
}
+ session_info->unique_session_token = GUID_random();
+
session_info->credentials = NULL;
talloc_steal(mem_ctx, session_info);