mirror of
https://github.com/kanidm/kanidm.git
synced 2025-02-23 20:47:01 +01:00
note non-validity of SPNs as email addresses per rfc
This commit is contained in:
parent
4e8aa2dd10
commit
230396c20c
|
@ -468,8 +468,10 @@ of an identity provider from the hostname alone, and seems to be intended to
|
||||||
support dynamic client registration flows for large public identity providers.
|
support dynamic client registration flows for large public identity providers.
|
||||||
|
|
||||||
Kanidm v1.5.1 and later can respond to WebFinger requests, using a user's SPN as
|
Kanidm v1.5.1 and later can respond to WebFinger requests, using a user's SPN as
|
||||||
the account (eg: `user@idm.example.com`). This *does not* match on email
|
[an `acct` URI][rfc7565] (eg: `acct:user@idm.example.com`).
|
||||||
addresses, because they are not required by Kanidm nor guaranteed to be unique.
|
[As per RFC 7565][rfc7565s4], there is no guarantee that account IDs are valid
|
||||||
|
for any particular application protocol (such as email), unless an administrator
|
||||||
|
explicitly provides it.
|
||||||
|
|
||||||
When setting up an application to authenticate with Kanidm, WebFinger **does not
|
When setting up an application to authenticate with Kanidm, WebFinger **does not
|
||||||
add any security** over configuring an OpenID Discovery URL directly. In an OIDC
|
add any security** over configuring an OpenID Discovery URL directly. In an OIDC
|
||||||
|
@ -529,3 +531,6 @@ difficult to use with Kanidm:
|
||||||
Because of these issues, we recommend that applications support *directly*
|
Because of these issues, we recommend that applications support *directly*
|
||||||
configuring OIDC using a Discovery URL or OAuth 2.0 Authorisation Server
|
configuring OIDC using a Discovery URL or OAuth 2.0 Authorisation Server
|
||||||
Metadata URL instead of WebFinger.
|
Metadata URL instead of WebFinger.
|
||||||
|
|
||||||
|
[rfc7565]: https://datatracker.ietf.org/doc/html/rfc7565
|
||||||
|
[rfc7565s4]: https://datatracker.ietf.org/doc/html/rfc7565#section-4
|
||||||
|
|
Loading…
Reference in a new issue