Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify what happens after authentication. #122

Merged
merged 2 commits into from
Nov 23, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1610,10 +1610,10 @@ <h2>Verification Relationships</h2>
<h2>Authentication</h2>

<p>
The `authentication` [=verification relationship=] is used to
specify how the [=controller=] is expected to be [=authenticated=], for
purposes such as logging into a website or engaging in any sort of
challenge-response protocol.
The `authentication` [=verification relationship=] is used to specify how the
[=controller=] is expected to be [=authenticated=], for purposes such as logging
into a website or engaging in any sort of challenge-response protocol. The
processing performed following authentication is application-specific.
</p>

<dl>
Expand Down Expand Up @@ -1663,10 +1663,6 @@ <h2>Authentication</h2>
}
</pre>

<p>
If authentication is established, it is up to the application to decide what to
do with that information.
</p>
<p>
This is useful to any entity verifying authentication that needs to check
whether an entity that is attempting to [=authenticate=] is presenting a valid
Expand Down