Hi there,
We're trying to automate the initialization of our AnvilConnect setup thus using the CLI quite intensively but have stumbled upon a few problems.
This is the code of the client we're trying to register:
nvl client:register \
--trusted \
--name "CMS" \
--uri https://cms-test/app \
--logo-uri http://toto.com \
--application-type web \
--response-type "id_token token" \
--grant-type implicit \
--default-max-age 3600 \
--redirect-uri "https://cms-test/app/" \
--redirect-uri "http://localhost:8082/app/" \
--post-logout-redirect-uri "https://cms-test/app" \
--post-logout-redirect-uri "http://localhost:8082/app"
This lead to a Validation Error. Since the error is not detailed, we logged the error in the connect-cli Clients API and this is the result:
{
"valid": false,
"errors": {
"redirect_uris": {
"attribute": "conform",
"property": "redirect_uris",
"actual": ["https://cms-test/app/","http://localhost:8082/app/"],
"message": "Must follow guidelines in OpenID Connect Registration 1.0 specification for client metadata"
}
},
"name": "ValidationError",
"message": "Validation error.",
"statusCode": 400
}
Nothing seems wrong to me but I might be missing something... Or is the CLI error message wrong?
Since the CLI was failing, we asked the API using POST /v1/clients with the data and the correct access token:
{
"trusted": true,
"client_name": "CMS",
"client_uri": "https://cms-test/app",
"logo_uri": "http://toto.com",
"application_type": "web",
"response_types": ["id_token token"],
"grant_types": ["implicit"],
"default_max_age": 3600,
"redirect_uris": ["https://cms-test/app/", "http://localhost:8082/app/"],
"post_logout_redirect_uris": ["https://cms-test/app","http://localhost:8082/app"]
}
But still got a Validation error.
Any idea or suggestion?
Hi there,
We're trying to automate the initialization of our AnvilConnect setup thus using the CLI quite intensively but have stumbled upon a few problems.
This is the code of the client we're trying to register:
This lead to a
Validation Error. Since the error is not detailed, we logged the error in the connect-cli Clients API and this is the result:{ "valid": false, "errors": { "redirect_uris": { "attribute": "conform", "property": "redirect_uris", "actual": ["https://cms-test/app/","http://localhost:8082/app/"], "message": "Must follow guidelines in OpenID Connect Registration 1.0 specification for client metadata" } }, "name": "ValidationError", "message": "Validation error.", "statusCode": 400 }Nothing seems wrong to me but I might be missing something... Or is the CLI error message wrong?
Since the CLI was failing, we asked the API using
POST /v1/clientswith the data and the correct access token:{ "trusted": true, "client_name": "CMS", "client_uri": "https://cms-test/app", "logo_uri": "http://toto.com", "application_type": "web", "response_types": ["id_token token"], "grant_types": ["implicit"], "default_max_age": 3600, "redirect_uris": ["https://cms-test/app/", "http://localhost:8082/app/"], "post_logout_redirect_uris": ["https://cms-test/app","http://localhost:8082/app"] }But still got a
Validation error.Any idea or suggestion?