Specification of unpadded Base64

This commit is contained in:
Richard van der Hoff 2017-03-01 08:50:07 +00:00
parent 39f177b5eb
commit da686ba4eb
5 changed files with 66 additions and 5 deletions

View file

@ -267,7 +267,7 @@ This is less secure than the client doing it itself, but may be useful where thi
The identity service will happily sign invitation details with a request-specified ed25519 private key for you, if you want it to. It takes URL-encoded POST parameters:
- mxid (string, required)
- token (string, required)
- private_key (string, required): The unpadded base64-encoded private key.
- private_key (string, required): The private key, encoded as `Unpadded base64`_.
It will look up ``token`` which was stored in a call to ``store-invite``, and fetch the sender of the invite. It will then respond with JSON which looks something like::
@ -281,3 +281,5 @@ It will look up ``token`` which was stored in a call to ``store-invite``, and fe
},
"token": "abc123"
}
.. _`Unpadded Base64`: ../appendices.html#unpadded-base64