Update patch set 16

Patch Set 16:

(1 comment)

Patch-set: 16
Attention: {"person_ident":"Gerrit User 27900 \u003c27900@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_28356\u003e replied on the change"}
Attention: {"person_ident":"Gerrit User 28356 \u003c28356@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_28356\u003e replied on the change"}
This commit is contained in:
Gerrit User 28356 2024-04-12 15:58:27 +00:00 committed by Gerrit Code Review
parent 3bc9259256
commit da85507633
1 changed files with 18 additions and 0 deletions

View File

@ -33,6 +33,24 @@
"message": "IMHO this is even worse. Idea of having project/role info coming from external identity manager is to centralize identity mgmt to avoid splitting data across systems (users in one system vs projects/roles in another system). With this statement you blow whole idea.",
"revId": "43559b813528604c247f67258e9f6daa81566bb8",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "53fd4d31_3e983ea8",
"filename": "specs/keystone/2024.1/federated-identity-mapping-support-project-json-definition.rst",
"patchSetId": 16
},
"lineNbr": 103,
"author": {
"id": 28356
},
"writtenOn": "2024-04-12T15:58:27Z",
"side": 1,
"message": "No, we are not blowing anything. I am not sure what you do not understand; would you mind explaining in details?\n\nThe hard-coded projects receive the role definition from the IdP as well. The difference, is that, as explained in the spec, it is a rigid structure, and with the option to receive a JSON, we can have as many projects definitions as we want.",
"parentUuid": "21bc093f_2ada9c5d",
"revId": "43559b813528604c247f67258e9f6daa81566bb8",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}