Skip to content
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

fix(jans-keycloak-link): not able to connect keycloack server #10742

Open
manojs1978 opened this issue Jan 25, 2025 · 1 comment
Open

fix(jans-keycloak-link): not able to connect keycloack server #10742

manojs1978 opened this issue Jan 25, 2025 · 1 comment
Assignees
Labels
comp-jans-keycloak-link Touching folder /jans-keycloak-link kind-bug Issue or PR is a bug in existing functionality
Milestone

Comments

@manojs1978
Copy link
Contributor

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. install jans/flex nighlty
  2. see error in jans-keycloak-link log

Expected behavior
should not get any error

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: ubuntu 22
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]
  • DB mysql

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

25-01-2025 09:20:54.968 ERROR keycloak.link.timer.JansKeycloakLinkTimer JansKeycloakLinkTimer.java:214- not able to connect keycloack server : Unsupported grantType:  (only password and client_credentials are supported)
java.lang.IllegalArgumentException: Unsupported grantType:  (only password and client_credentials are supported)
        at org.keycloak.admin.client.Config.checkGrantType(Config.java:124)
        at org.keycloak.admin.client.KeycloakBuilder.grantType(KeycloakBuilder.java:78)
        at io.jans.keycloak.link.server.service.KeycloakService.getKeycloakInstance(KeycloakService.java:59)
        at io.jans.keycloak.link.server.service.KeycloakService$Proxy$_$$_WeldSubclass.getKeycloakInstance$$super(Unknown Source)
        at jdk.internal.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)
        at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51)
        at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78)
        at org.jboss.weld.probe.InvocationMonitor.monitor(InvocationMonitor.java:125)
        at jdk.internal.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)
        at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73)
        at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84)
        at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72)

log.zip

@mo-auto mo-auto added comp-jans-keycloak-link Touching folder /jans-keycloak-link kind-bug Issue or PR is a bug in existing functionality labels Jan 25, 2025
@devrimyatar
Copy link
Contributor

@manojs1978 @shekhar16 I did four installations and faced this issue only once.

@moabu moabu added this to the next-release milestone Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-keycloak-link Touching folder /jans-keycloak-link kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants