issue-1357: Add attribute allowpublic to uaa Client resource - #1366
issue-1357: Add attribute allowpublic to uaa Client resource#1366damzog wants to merge 3 commits into
Conversation
|
As far as I can see, the code looks good and the existing tests run. |
|
@Lokowandtg I have added explicit setting and validating the flag in an existing integration test. I actually tried to run the integration test against a kind-deployment (setting it up actually caused me some trouble) but I could not figure out the required values for TEST_ADMIN_CLIENTID , TEST_ADMIN_CLIENTSECRET ( I guess a client needed to be created first which would require to know uaa admin user name ) maybe if you can share some light into this? Anyway the code is so simple it might even run without having tested it ... |
|
Running the integration test in my landscape fails, as there are two clients created, only the second one having the "allowpublic" set, but the first client is used for validation and results in a null value. ` |
|
Do you know when (in which version of CAPI) "allowpublic" was added? A guard-annotation might be needed. |
|
@Lokowandtg that is actually embarrassing. I will change the test case as you propose. The allowPublic attribute (allowing the client_secret to be omitted when public clients use PKCE with code_challenge_method=S256) was introduced in UAA version 75.21.0., see release notes |
No description provided.