Add documentation for new AS Notification/Profile feature
This commit is contained in:
@@ -7,6 +7,7 @@ https://firebase.google.com/
|
||||
| Authentication | Yes |
|
||||
| Directory | No |
|
||||
| Identity | Yes |
|
||||
| Profile | No |
|
||||
|
||||
## Requirements
|
||||
This backend requires a suitable Matrix client capable of performing Firebase authentication and passing the following
|
||||
|
||||
@@ -13,6 +13,7 @@ For NetIQ, replace all the `ldap` prefix in the configuration by `netiq`.
|
||||
| Authentication | Yes |
|
||||
| Directory | Yes |
|
||||
| Identity | Yes |
|
||||
| Profile | Yes |
|
||||
|
||||
## Getting started
|
||||
### Base
|
||||
|
||||
@@ -13,6 +13,7 @@ To integrate this backend with your webapp, you will need to implement three spe
|
||||
| Authentication | Yes |
|
||||
| Directory | Yes |
|
||||
| Identity | Yes |
|
||||
| Profile | No |
|
||||
|
||||
## Configuration
|
||||
| Key | Default | Description |
|
||||
|
||||
@@ -11,6 +11,7 @@
|
||||
| Authentication | No |
|
||||
| Directory | Yes |
|
||||
| Identity | Yes |
|
||||
| Profile | Yes |
|
||||
|
||||
Due to the implementation complexity of supporting arbitrary hashing/encoding mechanisms or auth flow, Authentication
|
||||
will be out of scope of SQL Identity stores and should be done via one of the other identity stores, typically
|
||||
|
||||
@@ -7,6 +7,7 @@ Synapse's Database itself can be used as an Identity store.
|
||||
| Authentication | No |
|
||||
| Directory | Yes |
|
||||
| Identity | Yes |
|
||||
| Profile | Yes |
|
||||
|
||||
Authentication is done by Synapse itself.
|
||||
|
||||
|
||||
@@ -10,6 +10,7 @@ Two types of connections are required for full support:
|
||||
| Authentication | Yes |
|
||||
| Directory | Yes |
|
||||
| Identity | Yes |
|
||||
| Profile | No |
|
||||
|
||||
## Requirements
|
||||
- [Wordpress](https://wordpress.org/download/) >= 4.4
|
||||
|
||||
Reference in New Issue
Block a user