| ... | ... | @@ -10,7 +10,7 @@ A federated user is a user which can authenticate with multiple servers. This me |
|
|
|
DjangoLDP achieves this using [OpenID Connect (OIDC)](https://openid.net/connect/). In OIDC users are globally identifiable via a "WebFinger ID". An example is `alice@aliceswebsite.com`, where `alice` is the username, hosted by the provider `aliceswebsite.com`. Using OIDC Alice can authenticate with `aliceswebsite.com`, authorising `bobswebsite.com` to make use of her account
|
|
|
|
|
|
|
|
When implementing authentication in your own application, you have two options:
|
|
|
|
* Using or extending DjangoLDP-Account, a DjangoLDP package modelling federated users
|
|
|
|
* [Using or extending DjangoLDP-Account](https://git.startinblox.com/djangoldp-packages/djangoldp/wikis/guides/authentication#using-djangoldp-accounts-authentication), a DjangoLDP package modelling federated users
|
|
|
|
* [Using your own user model](https://git.startinblox.com/djangoldp-packages/djangoldp/wikis/guides/authentication#using-your-own-user-model) & defining the authentication behaviour yourself
|
|
|
|
|
|
|
|
Regardless of the choice you make, DjangoLDP will extend your user model to include a method `webid` which returns uri to identify your user, for example `https://aliceswebsite.com/users/alice`. This is used in `LDPSerializer` so that views are returned in linked-data format, describing the semantics and location of resources in the response
|
| ... | ... | |
| ... | ... | |
