comparison mod_http_oauth2/README.markdown @ 5507:209299fd81e1

mod_http_oauth2: Fix messed up section about redirect_uris requirements
author Kim Alvefur <zash@zash.se>
date Thu, 01 Jun 2023 20:02:45 +0200
parents 37621c6e5c08
children 56803acfa638
comparison
equal deleted inserted replaced
5506:37621c6e5c08 5507:209299fd81e1
123 123
124 : **MUST** contain at least one valid URI. Different rules apply 124 : **MUST** contain at least one valid URI. Different rules apply
125 depending on the value of `application_type`: 125 depending on the value of `application_type`:
126 126
127 `web` 127 `web`
128 : `redirect_uris` **MUST** match one of: - Loopback HTTP URI, 128 : `redirect_uris` **MUST** be `https://` URIs and **MUST** use the
129 e.g. `http://127.0.0.1/` or `http://[::1]` - 129 same hostname part as the `client_uri`.
130 Application-specific scheme, e.g. `com.example.app:/` - The 130
131 special OOB URI `urn:ietf:wg:oauth:2.0:oob` 131 `native`
132
133 : `redirect_uris` **MUST** match one of:
134
135 - Loopback HTTP URI, e.g. `http://127.0.0.1/` or
136 `http://[::1]`
137 - Application-specific scheme, e.g. `com.example.app:/`
138 - The special OOB URI `urn:ietf:wg:oauth:2.0:oob`
132 139
133 `application_type` 140 `application_type`
134 141
135 : Optional, defaults to `web`. Determines further restrictions for 142 : Optional, defaults to `web`. Determines further restrictions for
136 `redirect_uris`. The following values are supported: 143 `redirect_uris`. The following values are supported: