|
1 | | -## OpenID Federation Tools (draft 44) |
| 1 | +# OpenID Federation Tools (draft 44) |
2 | 2 |
|
3 | 3 | To use it, create an instance of the class `\SimpleSAML\OpenID\Federation`. |
4 | 4 |
|
@@ -62,7 +62,7 @@ class Test |
62 | 62 | } |
63 | 63 | ``` |
64 | 64 |
|
65 | | -### Trust chain resolver |
| 65 | +## Trust Chain Resolver |
66 | 66 |
|
67 | 67 | Once you have a `\SimpleSAML\OpenID\Federation` instantiated, you can continue |
68 | 68 | with using available tools. The first tool we will take a look at is the Trust |
@@ -159,7 +159,7 @@ if (is_null($metadata)) { |
159 | 159 | If getting metadata results in an exception, the metadata is considered invalid |
160 | 160 | and is to be discarded. |
161 | 161 |
|
162 | | -### Additional verification of signatures |
| 162 | +## Additional Verification of Signatures |
163 | 163 |
|
164 | 164 | The whole trust chain (each entity statement) has been verified using public |
165 | 165 | keys from JWKS claims in configuration / subordinate statements. As per |
@@ -196,7 +196,7 @@ try { |
196 | 196 |
|
197 | 197 | ``` |
198 | 198 |
|
199 | | -### Fetching Trust Marks |
| 199 | +## Fetching Trust Marks |
200 | 200 |
|
201 | 201 | Federation tools expose Trust Mark Fetcher, which you can use to dynamically |
202 | 202 | fetch or refresh (short-living) Trust Marks. |
@@ -235,7 +235,7 @@ try { |
235 | 235 |
|
236 | 236 | ``` |
237 | 237 |
|
238 | | -### Validating Trust Marks |
| 238 | +## Validating Trust Marks |
239 | 239 |
|
240 | 240 | Federation tools expose Trust Mark Validator with several methods for validating |
241 | 241 | Trust Marks, with the most common one being the one to validate Trust Mark for |
@@ -284,4 +284,4 @@ try { |
284 | 284 | return; |
285 | 285 | } |
286 | 286 |
|
287 | | -``` |
| 287 | +``` |
0 commit comments