ForgeRock / openid

Trying OpenAM's OpenID Connect 1.0 features
22 stars 15 forks source link

Issue #8 Add client_name for dynamic registration #9

Closed markcraig closed 8 years ago

markcraig commented 8 years ago

This patch adds a client_name for dynamic registration.

It also takes advantage of a setting in OpenAM that makes it unnecessary to get an access token before registering.

This is an example of a Registration Response:

{
  "default_max_age_enabled": false,
  "subject_type": "public",
  "default_max_age": 1,
  "application_type": "web",
  "jwt_token_lifetime": 0,
  "registration_client_uri": "http://openam.example.com:8088/openam/oauth2/connect/register?client_id=9540e9cc-c492-4142-b7f6-aecd66523847",
  "client_type": "Confidential",
  "redirect_uris": [
    "http://openam.example.com:8088/openid/cb-basic.html",
    "http://openam.example.com:8088/openid/cb-implicit.html"
  ],
  "registration_access_token": "c5063095-63aa-415d-8a78-22f6a7cbf094",
  "client_id": "9540e9cc-c492-4142-b7f6-aecd66523847",
  "token_endpoint_auth_method": "client_secret_basic",
  "public_key_selector": "x509",
  "client_secret_expires_at": 0,
  "access_token_lifetime": 0,
  "refresh_token_lifetime": 0,
  "authorization_code_lifetime": 0,
  "scopes": [
    "address",
    "phone",
    "openid",
    "profile",
    "email"
  ],
  "client_secret": "6edaa85f-da51-473e-9df1-91ad7b154631",
  "client_name": "Dynamically Registered Client",
  "id_token_signed_response_alg": "HS256",
  "response_types": [
    "code"
  ]
}
markcraig commented 8 years ago

@forgerock-chris , is this PR okay with you?

forgerock-chris commented 8 years ago

Yep looks good, got the /oauth2/.well-known default path change in too, nice one. Cheers.

markcraig commented 8 years ago

Thanks.