| ... | ... | @@ -92,3 +92,5 @@ More is happening under the surface, as DjangoLDP comes packaged with [django-oi |
|
|
|
If you would like users from other sites to log into your site, then you will need to implement the endpoints of the Relying Party (RP)
|
|
|
|
|
|
|
|
An example implementation of the Relying Party endpoint [can be found in DjangoLDP-Account](https://git.startinblox.com/djangoldp-packages/djangoldp-account/blob/master/djangoldp_account/endpoints/rp_login.py). When the user submits their webfinger ID or OIDC provider to the [login form](https://git.startinblox.com/djangoldp-packages/djangoldp-account/blob/master/djangoldp_account/templates/registration/login.html), the endpoint utilises [PyOIDC](https://pyoidc.readthedocs.io/en/latest/examples/rp.html) to discover the issuer of the provider, and provides the callback function in this endpoint to log the user in once authenticated
|
|
|
|
|
|
|
|
It's important to note that once the federated user has successfully logged in, their urlid should be set to that of their OIDC provider, so that their id is maintained as from the distant source |
|
|
\ No newline at end of file |
