f02e4c2e9c
both registers are excluded from auth
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
5374030cc0
Drop application/x-form-www-urlencoded in v2
7 years ago
2d11217d4e
Typo
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
8af35be13f
Typo
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
fe14d3c9f0
Spec terms response
7 years ago
786d5bc281
rewrite UI auth tradeoffs
7 years ago
45d630951c
back to M_TERMS_NOT_SIGNED
7 years ago
83bb3861ba
line wrap
7 years ago
4be283ccb3
Typing
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
f95197b422
make the many-anded sentence a list
7 years ago
10a6a59a12
Deprecate `bind_email` / `bind_msisdn`
7 years ago
b5326de1c4
Exclude requestToken endpoints from auth requirement
7 years ago
21b9eaf8de
No custom HTTP headers
...
Use the obvious way: in the same place as the ID server address
7 years ago
2694bb1090
Add really horrible custom HTTP header
...
for giving the IS token to the HS
7 years ago
58cf083a6a
backwards compat
7 years ago
6273868323
Clarify v1 API deprecation
7 years ago
4edf826c93
Capitalise on our identifiers
7 years ago
ba7047ce77
Clarify we must be accepting HS auth
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
1d75828c71
Clarify what to do if no (new) docs
7 years ago
af691b5a8a
Clarify this applies to 2134
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
57094276ce
Typing hard is
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
9e0d8b9cb2
Use M_CONSENT_NOT_GIVEN
...
No idea where I got the other one from: we already have one in the
spec, so use it.
7 years ago
0dae2d5812
GET terms must be unauthed.
...
Detail process for new auth (don't register until consent given).
Specifically mention the authentication header.
7 years ago
6f374dc981
Re-write for OpenID auth
7 years ago
2c09580e27
line wrap
7 years ago
abb407145a
HS docs must be added too
...
also, unbind must not error when called by HSes and proxy terms token
7 years ago
8ae47557c9
s/Third Party/Accepted/
7 years ago
2555801458
m.third_party_terms -> m.accepted_terms
...
as it will have the HS's terms too
7 years ago
4ba9b2a599
perfix
7 years ago
a63e4420eb
Linkify
...
Co-Authored-By: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
7 years ago
9ca3ccc81c
Add requirments section for de-duping between services.
7 years ago
d4ca0c237a
Specify ID grammar and add comma
7 years ago
276e2b6843
Typo
...
Co-Authored-By: Travis Ralston <travpc@gmail.com>
7 years ago
cf48030d1f
One more tradeoff
7 years ago
32c7fc638d
you have a number now
7 years ago
23af87e9fc
Proposal for IS & IM TOS API
7 years ago
ace94f02b7
Merge pull request #2132 from jimmycuadra/clarify-m.key.verification.start
...
Clarify the distinction between *m.key.verification.start* and its *m.sas.v1* variant.
7 years ago
8246383330
Fix typos in changelog entry.
7 years ago
204601d9a4
Merge pull request #2133 from matrix-org/travis/fix-olm-2
...
Fix link to Olm signing specification
7 years ago
ffdd8dfe01
Merge pull request #2137 from matrix-org/identity_service/release-r0.2.1
...
Identity r0.2.1
7 years ago
d09af5b191
Identity r0.2.1
7 years ago
954a5607c3
Merge pull request #2136 from ma1uta/master
...
Fix typo.
7 years ago
c63b5aff69
Create 2136.clarification
7 years ago
802b90d113
Typo.
7 years ago
8affb23e5e
Address feedback from code review.
...
* Switch "an SAS" back to "a SAS"
* Remove the `next_method` field from m.key.verification.start$m.sas.v1
but add additional clarification to its description on
m.key.verification.start that it is never present for methods that
verify keys both ways.
7 years ago
6f460ad70a
minus spec
...
according to the apache .htaccess we use
7 years ago
33ca891e71
Fix link to Olm signing specification
...
See https://github.com/matrix-org/matrix.org/issues/478
7 years ago
5384b61d95
Fix style issues brought up during code review.
...
Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
7 years ago
bc71dacaf4
Clarify the distinction between *m.key.verification.start* and its *m.sas.v1* variant.
...
Currently the *m.key.verification.start* event appears twice with the
exact same title, in the "Key verification framework" section and the
"Short Authentication (SAS) verification" section. It's not immediately
clear that the first occurrence describes the format of the event in
general terms and that the second occurrence describes the fields when
the *m.sas.v1* verification method is being used. This is a similar
relationship to the *m.room.message* event and its various *msgtype*
variants.
This commit does three things:
* It tweaks the generation of the documentation to change the title
of the second occurrence of *m.key.verification.start* to
distinguish it from the first.
* It updates the language in the description of the two versions of the
event to better describe the relationship between the two.
* It adds the optional `next_method` field to the schema of the
*m.sas.v1* variant, as specified in the general form of
*m.key.verification.start*.
Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
7 years ago
b807e1cbe5
Merge pull request #2129 from jimmycuadra/conditionally-required-url-fields
...
Remove the "required" designation from the `url` field of certain m.room.message msgtypes.
7 years ago
David Baker