problem: User-Id field in zap response is not populated #1711
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
problem: zauth tests do not check User-Id metadata
Solution: update the PLAIN and CURVE tests to fetch and verify the
User-Id metadata set by ZAP
problem: User-Id field in zap response is not populated.
According to ZAP spec:
user id: this MAY provide the user identity in case of a 200 status, for
use by applications. For other statuses, it SHALL be empty.
Solution: This adds a char pointer in the zap request struct that can
point to the the username, client_key, or principal fields.
With this change zframe_meta(frame, "User-Id") returns the public key
for a connection. This enables a use case where you have a long lived
connection authenticated by a key or password and want to verify that the
user/key still exists.