Apply suggestions from code review
Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
This commit is contained in:
parent
c124462747
commit
cbd761df17
2 changed files with 2 additions and 2 deletions
|
@ -40,7 +40,7 @@ administrator to configure where the CAS server is and the REST
|
|||
endpoints which consume the ticket.
|
||||
|
||||
Homeservers may optionally expose multiple possible SSO options for
|
||||
the user to persue, typically in the form of several "login with $service"
|
||||
the user to pursue, typically in the form of several "login with $service"
|
||||
buttons. These services, or "identity providers" (IdPs), are typically
|
||||
OpenID Connect, though the exact protocol used is not a concern for this
|
||||
specification.
|
||||
|
|
|
@ -20,7 +20,7 @@ For the brands listed here, the `identifier` would be used as the `brand` value
|
|||
under `m.login.sso`'s flow.
|
||||
|
||||
Note that each brand may have their own requirements for how they are represented by clients, such as
|
||||
Facebook/Twitter wanting their signature blues for button backgrounds whereas Github is not as particular
|
||||
Facebook/Twitter wanting their signature blues for button backgrounds whereas GitHub is not as particular
|
||||
about the press requirements. Clients should not rely on this document for guidance on press requirements
|
||||
and instead refer to the brands individually.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue