-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the current release compatible with the 3.1.0 APIM version? #11
Comments
I have encountered the same issue recently, it would be great to have a feedback about this. |
I have the same issue ... your help/support is highly appreciated |
here's the error: |
I just modified the plugin to make it work on 3.1.0, Can I contribute the changes? Thanks |
Hello all, Would you mind providing the code with the 3.1.x compatible version please? Also, if you have the updated doc? thanks a lot |
Hi @thomasbroussard @medkbadri, |
You can use https://github.com/wso2-extensions/apim-keymanager-keycloak/tree/3.0.0 for 3.1.0 release documents yet to be update according to the 3.1.0 configuration model |
Hi, thanks a lot for your answer. Just trying to update the configuration. Can you just confirm that to be compliant with 3.1.x conf model, I need to transform this part of the doc :
by (in deployment.toml)
Thanks a lot for all the great job (and for your answers) |
with the provided 3.0.0 branch, after compilation and configuration made as mentioned in my previous comment, i get a NPE, see the following stack trace.
Do you have an idea on how to troubleshoot this issue? Thanks |
Apparently, looking at the code, this line https://github.com/wso2/carbon-apimgt/blob/08ea54ec6be19ca6317027b09aaa566d6da85037/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/AbstractAPIManager.java#L2746 doesn't expect to have null values for API Scoped, which is possible in the current connector version. I just modified it tryin to have empty map instead of null to prevent NPE.
I think that this is the case when there are already defined APIs and we switch from default km to whatever else. |
I'm running into the same issue that @medkbadri originally mentioned ( @tharindu1st Are you saying that if we upgrade to 3.2.0, that by default it comes with the Keycloak connector that has these fixes? |
Hi @molinab297-unisys , |
Hi @tharindu1st , 2020-08-06 14:10:11,466] ERROR - KeycloakClient Error occurred while generating access token |
@tharindu1st I know API manager 3.2 still hasn't been officially released yet, but I'm on 3.2.0-RC3 right now, and I modified deployment.toml to look like this:
but API Manager seems to ignore these settings, as when I generate production keys for an application (in the devportal) it still uses the built-in key manager Am I missing something? Also will these docs eventually be updated to outline all of this? |
Hi @molinab297-unisys / @medkbadri / @ghfalcon7 / @smtibaa I have made a few enhancements and built a JAR artifact to support API Manager v3.1.0. You can find the Source and the Release here. The instructions on configuring the Keycloak connector with API Manager v3.1.0 can be found here. Please give a try and share the feedback. Furthermore, if you want to use WSO2 API Manager v3.2.0, you can follow the instructions here to configure the Keycloak key manager. Thanks in advance!!! |
Hello,
I'm both new to Keycloak and APIM. (I integrated Keycloak with some systems recently though)
My question is:
Thanks :)
The text was updated successfully, but these errors were encountered: