Repository navigation
Keycloak integration with zabbix. #25240
rohanrajnv
started this conversation in
Archive
Replies: 3 comments 2 replies
|
I have that same exact issue. |
0 replies
|
same exact issue |
1 reply
|
did you solve issue ? |
|
Hi, not sure if that helps, we are running into this issue when the encryption is not ok, and i could not make it work for Zabbix. It does work if you configure as follows IdP entity ID: https://KEYCLOAK/realms/REALMNAME Username attribute: WHATEVER YOU LIKE All tickboxes on, except "Encrypt Name ID" The rest according to your environment. Hope that helps |
1 reply
|
for you its working ? We are sorry... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the Issues:
I am trying to integrate Zabbix with the Key cloak for SSO. The Zabbix is redirecting to the key cloak page but getting the error
error=invalid_authn_request, reason=invalid_destination
Debug/Error Log:
2023-12-04 00:08:34,092 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-0) new JtaTransactionWrapper
2023-12-04 00:08:34,092 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-0) was existing? false
2023-12-04 00:08:34,092 DEBUG [org.keycloak.services.scheduled.ScheduledTaskRunner] (Timer-0) Executed scheduled task AbstractLastSessionRefreshStoreFactory$$Lambda$1293/0x00007f867baa37b8
2023-12-04 00:08:34,093 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-0) JtaTransactionWrapper commit
2023-12-04 00:08:34,093 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-0) JtaTransactionWrapper end
2023-12-04 00:08:34,814 DEBUG [io.netty.handler.ssl.SslHandler] (vert.x-eventloop-thread-3) [id: 0x51745b7a, L:/192.168.49.133:8443 - R:/192.168.49.3:23307] HANDSHAKEN: protocol:TLSv1.3 cipher suite:TLS_AES_256_GCM_SHA384
2023-12-04 00:08:34,815 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (executor-thread-36) new JtaTransactionWrapper
2023-12-04 00:08:34,815 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (executor-thread-36) was existing? false
2023-12-04 00:08:34,816 DEBUG [org.keycloak.protocol.saml.SamlService] (executor-thread-36) SAML GET
2023-12-04 00:08:34,816 DEBUG [org.keycloak.saml.SAMLRequestParser] (executor-thread-36) SAML Redirect Binding
2023-12-04 00:08:34,816 DEBUG [org.keycloak.saml.SAMLRequestParser] (executor-thread-36) <samlp:AuthnRequest
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
ID="ONELOGIN_475e9ba2aa834ef1804502fa5a066067b2a97725"
Version="2.0"
</samlp:AuthnRequest>
2023-12-04 00:08:34,818 DEBUG [org.keycloak.protocol.saml.SamlService] (executor-thread-36) ** login request
2023-12-04 00:08:34,818 DEBUG [org.keycloak.protocol.saml.SamlService] (executor-thread-36) verified request
2023-12-04 00:08:34,819 DEBUG [freemarker.cache] (executor-thread-36) TemplateLoader.findTemplateSource("template_en.ftl"): Not found
2023-12-04 00:08:34,819 DEBUG [freemarker.cache] (executor-thread-36) TemplateLoader.findTemplateSource("template.ftl"): Found
2023-12-04 00:08:34,819 DEBUG [freemarker.cache] (executor-thread-36) "template.ftl"("en", UTF-8, parsed): using cached since jar:file:/opt/keycloak/lib/lib/main/org.keycloak.keycloak-themes-21.0.2.jar!/theme/base/login/template.ftl hasn't changed.
2023-12-04 00:08:34,820 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (executor-thread-36) JtaTransactionWrapper commit
2023-12-04 00:08:34,820 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (executor-thread-36) JtaTransactionWrapper end
2023-12-04 00:08:34,820 WARN [org.keycloak.events] (executor-thread-36) type=LOGIN_ERROR, realmId=b7028da9-29ca-43a2-a17f-574264b20fec, clientId=null, userId=null, ipAddress=192.168.49.3, error=invalid_authn_request, reason=invalid_destination
2023-12-04 00:08:38,688 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-0) new JtaTransactionWrapper
2023-12-04 00:08:38,688 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-0) was existing? false
Version: 21.0.2
Expected behavior
We are sorry...
Invalid Request
« Back to Application
Actual behavior
The Login Page for the keycloke should be displayed.
How to Reproduce?
I have help with the any logs and details needed.
Anything else?
No response
All reactions