Closed ognjen-it closed 2 years ago
@ognjen-it could you tell us why you closed this issue? I am facing the same issue, but could not find a solution in the package.
because I don't think there are people here who are willing to help.. :( As you can see, you are the first one who post the comment here. Also, I asked in the Slack channel and noone answered me..
However, I will reopen it :)
Thanks for your response @ognjen-it . I have created a PR for this issue https://github.com/Nerzal/gocloak/pull/351
Wow, great to know that 🤗 Thank you for your effort to do that 🎉💯
I would like to know how to improve the gocloak, but I don't know the go language very well...
Hey @ognjen-it the PR is now merged. Once a release is created, you could update the package and try it out. Thanks for your support :)
Great! Thank you very much 🚀💯🥇 I will check it now and confirm if we can close this issue :)
V11.1.0 is released :)
I guess i can close this issue?
Yes, you can :) Thank all!
@Nerzal @ognjen-it Hey, When I am trying to partial update the ProtocolMappers (e.g add a new one on an existing client scope), I am facing the same issue in both V11.1.0 and V11.2.0 :)
Hi @chsavvaidis, @HimanshuM has resolved this problem with the PR #351. I'm not sure if I tested it, I have forgotten.
I need more time to check it because I deleted this piece of code..
Describe the bug We cannot create a mapper for Client or Client Scopes
To Reproduce Steps to reproduce the behavior:
Expected behavior We want to create a Client Scope with a special mapper
Screenshots With the above code, we can create a Client Scope but a mapper has not been created.
Additional context Keycloak version is 16.1.1, it's deployed with helm on Kubernetes 1.21 I didn't find any example of how to do it :(