Do not send empty auth when setting up cross-signing keys #29914
+3
−3
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.
My understanding from the spec is that no
auth
parameter should be sent when starting a UIA flow. This section says that "A client should first make a request with no auth parameter" and this is not what element-web is doing (since it is sending an auth parameter with an empty dictionary).In the upload cross-signing keys endpoint
documentation it says that type may be omitted if session is set, but in this specific case neither of the fields is set.
The proposed changes changes the empty dictionary for a
null
value in order to prevent theauth
field to be sent.Checklist
public
/exported
symbols have accurate TSDoc documentation.