uaa-concepts../source/uaa-concepts.html.md.erbSource: lines 174–220, under “Selecting the client grant type”. Five rows.
| Level | Hint | Value | From source |
|---|---|---|---|
| Table | header row | yes | <thead> |
| Table | row-header column | yes | column 1 names the grant type |
| Column 1 | role | key | <code> grant type names |
| Column 1 | width | about 30% | <th width="30%"> |
| Column 1 | wrap | avoid | identifiers such as client_credentials must not break at _ |
| Column 2 | role | prose | short phrases (“Developers building web apps”) |
| Column 3 | role | prose | sentences |
Cleanup needed: the implicit row (line 202) ends with </td> instead of
</tr>. Browsers ignore the stray end tag and close the row at the next
<tr>; strict parsers fail.
Deviations: the table has no class; it gets class="table", the
standard style, as every HTML table names its style (see
Template conventions).
In extension and native, the endpoint /oauth/token is marked as a path
(class="path"), which keeps it on one line (results, “Paths in table
cells”, 2026-10-12); passthrough keeps it as written.
implicit row is followed by the
client_credentials row, not merged into it.refresh_token row).client.additional_information)Source: lines 285–328. Five rows.
| Level | Hint | Value | From source |
|---|---|---|---|
| Table | header row | yes | <thead> |
| Table | row-header column | yes | column 1 names the key |
| Column 1 | role | key | <code> key names |
| Column 1 | width | about 25% | <th width="25%"> |
| Column 1 | wrap | avoid | key names |
| Column 2 | role | prose | sentences |
| Cell | block content | paragraphs | allowed providers row: <br/><br/> between two paragraphs |
Cleanup needed: none.
Deviations: in the allowed providers row, the two paragraphs separated
by <br/><br/> become two paragraphs. The text is unchanged; the line breaks
are a workaround standing in for a paragraph break. Decided after
comparing renderings: the double break is the end of a paragraph, with
paragraph spacing below it, so the cell holds two paragraphs. Passthrough
keeps the <br/><br/> (it applies cleanup only). Native pipe tables cannot
hold paragraphs, so native keeps <br /><br />.
The table also gets class="table", as the first one does. In extension
and native, the endpoints /identity-zones and /introspect are marked
as paths, as in the first table.
allowed providers row: the second paragraph starts “You can limit UAA
to only issue …”, separated from the first by a visible paragraph gap
(two <p> in extension and native; <br/><br/> in passthrough).vars.platform_name, twice).client.client_id link in the name row goes to the #clientid
anchor on the same page.<code>allowed providers="ldap"</code> keeps its quotes as straight
quotes inside code.