README.rst 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. Installation
  2. ============
  3. Dependencies can be installed using setup.py in the same way as synapse: see synapse/README.rst. For instance::
  4. sudo apt-get install build-essential python2.7-dev libffi-dev \
  5. sqlite3 libssl-dev python-virtualenv libxslt1-dev
  6. virtualenv -p python2.7 ~/.sydent
  7. source ~/.sydent/bin/activate
  8. pip install --upgrade pip
  9. pip install --upgrade setuptools
  10. pip install https://github.com/matrix-org/sydent/tarball/master
  11. Having installed dependencies, you can run sydent using::
  12. python -m sydent.sydent
  13. This will create a configuration file in sydent.conf with some defaults. You'll most likely want to change the server name and specify a mail relay.
  14. Defaults for SMS originators will not be added to the generated config file, these should be added in the form::
  15. originators.<country code> = <long|short|alpha>:<originator>
  16. Where country code is the numeric country code, or 'default' to specify the originator used for countries not listed. For example, to use a selection of long codes for the US/Canda, a short code for the UK and an alphanumertic originator for everywhere else::
  17. originators.1 = long:12125552368,long:12125552369
  18. originators.44 = short:12345
  19. originators.default = alpha:Matrix
  20. Requests
  21. ========
  22. The requests that synapse servers and clients submit to the identity server are, briefly, as follows:
  23. Request the validation of your email address::
  24. curl -XPOST 'http://localhost:8090/_matrix/identity/api/v1/validate/email/requestToken' -H "Content-Type: application/json" -d '{"email": "matthew@arasphere.net", "client_secret": "abcd", "send_attempt": 1}'
  25. {"success": true, "sid": "1"}
  26. (Receive 943258 by mail)
  27. Use this code to validate your email address::
  28. curl -XPOST 'http://localhost:8090/_matrix/identity/api/v1/validate/email/submitToken' -H "Content-Type: application/json" -d '{"token": "943258", "sid": "1", "client_secret": "abcd"}'
  29. {"success": true}
  30. Use the validated email address to bind it to a matrix ID::
  31. curl -XPOST 'http://localhost:8090/_matrix/identity/api/v1/3pid/bind' -H "Content-Type: application/json" -d '{"sid": "1", "client_secret": "abcd", "mxid": "%40matthew%3amatrix.org"}'
  32. Lookup::
  33. curl 'http://localhost:8090/_matrix/identity/api/v1/lookup?medium=email&address=henry%40matrix.org'
  34. Fetch pubkey key for a server::
  35. curl http://localhost:8090/_matrix/identity/api/v1/pubkey/ed25519:0
  36. Internal bind api
  37. -----------------
  38. It is possible to enable an internal API which allows identifiers to be bound
  39. to matrix IDs without any validation. This is open to abuse, so is disabled by
  40. default, and when it is enabled, is available only on a separate socket which
  41. is bound to 'localhost' by default.
  42. To enable it, configure the port in the config file. For example::
  43. [http]
  44. internalapi.http.port = 8091
  45. To use it::
  46. curl -XPOST 'http://localhost:8091/_matrix/identity/internal/bind' -H "Content-Type: application/json" -d '{"address": "matthew@arasphere.net", "medium": "email", "mxid": "@matthew:matrix.org"}'
  47. The response has the same format as ``/_matrix/identity/api/v1/3pid/bind``.