comparison mod_http_oauth2/README.markdown @ 5494:1bcf755c7bae

mod_http_oauth2: Add an example of client registration
author Kim Alvefur <zash@zash.se>
date Fri, 26 May 2023 15:49:39 +0200
parents cae3bb3dd45f
children efe9e741f222
comparison
equal deleted inserted replaced
5493:cae3bb3dd45f 5494:1bcf755c7bae
125 - Application-specific scheme, e.g. `com.example.app:/` 125 - Application-specific scheme, e.g. `com.example.app:/`
126 - The special OOB URI `urn:ietf:wg:oauth:2.0:oob` 126 - The special OOB URI `urn:ietf:wg:oauth:2.0:oob`
127 - Informative URIs such as policy and terms of service **MUST** use 127 - Informative URIs such as policy and terms of service **MUST** use
128 the same scheme (i.e. `https://`) and hostname as the `client_uri`. 128 the same scheme (i.e. `https://`) and hostname as the `client_uri`.
129 129
130 #### Registration Example
131
132 In short registration works by POST-ing a JSON structure describing your
133 client to an endpoint:
134
135 ``` bash
136 curl -sSf https://xmpp.example.net/oauth2/register \
137 -H Content-Type:application/json \
138 -H Accept:application/json \
139 --data '
140 {
141 "client_name" : "My Application",
142 "client_uri" : "https://app.example.com/",
143 "redirect_uris" : [
144 "https://app.example.com/redirect"
145 ]
146 }
147 '
148 ```
149
130 ### Supported flows 150 ### Supported flows
131 151
132 Various flows can be disabled and enabled with 152 Various flows can be disabled and enabled with
133 `allowed_oauth2_grant_types` and `allowed_oauth2_response_types`: 153 `allowed_oauth2_grant_types` and `allowed_oauth2_response_types`:
134 154