I think it should be same consistent behaviour on all places. Probably we should make it to what is used for clients (id is allowed) and improve realms and users to allow it too.
Feel free to create JIRA for this.
Marek
On 10/12/15 14:24, Juraj Janosik wrote:
Hi all,please, could somebody clarify issue (see bottom of the mail) discovered in version 1.6.1.Final?
The same behavior is detected in version 1.7.0.Final.
This behavior differs from a Create a New User where the JSON body parameter "id" is skipped.
Thanks a lot.
Best regards,
Juraj
2015-11-12 10:32 GMT+01:00 Juraj Janosik <juraj.janosik77@gmail.com>:
If I set the parameter "id" in the request body (see example below),Hi,I want to clarify the "Create a new client" via REST API
especially for body parameter "id" from "ClientRepresentation".
the value is set to the client. No new id value is generated for the client, which is the typically behavior of "Create a new role for the realm or client" and "Create a new user".
Is this a correct behavior?
Tested data example:
"Create Client":
"method":"POST","url":"<URL>:<PORT>/auth/admin/realms/<REALM>/clients"
"body":
"{
"id":"3",
"clientId":"testclient-3",
"name": "testclient-3",
"description": "TESTCLIENT-3",
"enabled": true,
"redirectUris":[ "\\" ],
"publicClient": true
}"
"headers":
[["Content-Type","application/json"],
["Authorization","Bearer <ACCESS_TOKEN>]]
Output for GET clients looks like:
{
"id": "3",
"clientId": "testclient-3",
"name": "testclient-3",
"description": "TESTCLIENT-3",
"surrogateAuthRequired": false,
"enabled": true,
"clientAuthenticatorType": "client-secret",
"redirectUris":
[
"\"
],
"webOrigins":
[
],
"notBefore": 0,
"bearerOnly": false,
"consentRequired": false,
"serviceAccountsEnabled": false,
"directGrantsOnly": false,
"publicClient": true,
"frontchannelLogout": false,
"attributes":
{
},
...
Thanks a lot.
Best Regards,
Juraj
_______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user