Project

Profile

Help

Issue #438

closed

Call flow for consumer is missing for authenticated agent amqp communication scenario

Added by mkovacik@redhat.com about 9 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
2.4 Beta
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

Description of problem:
A detailed description for the authenticated agent amqp scenario is missing in current docs (see #URL) w.r. consumer create call-flow

Expected results:
New page describing in detail how to perform consumer register in order to allow consumers (custom) agent to talk with Pulp over amqp with Digest authentication.
Especially, the page should describe:
- the initial consumer create/POST request should contain pub_key attribute
holding consumer's public key used later on for the Digest authentication
- how the consumer should obtain server's public key for Digest authentication
- how these key pairs should be used to compute the Digest Authentication for
consumer's agent communication with Pulp broker.

+ This bug was cloned from Bugzilla Bug #1101639 +

Also available in: Atom PDF