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

SAML with keycloak #365

Open
VincentSC opened this issue Feb 10, 2025 · 1 comment
Open

SAML with keycloak #365

VincentSC opened this issue Feb 10, 2025 · 1 comment

Comments

@VincentSC
Copy link

As only Okta is described and seemingly only one person tried Authentik, I'm quite lost in how to configure this.

I eventually found that this is an IDP Initiated login, which Keycloak describes here: https://www.keycloak.org/docs/latest/server_admin/index.html#idp-initiated-login - here I picked the first option, "Assertion Consumer Service POST Binding URL", to put the url https://<domain>/app/login.php. I have configured many SAML-SSO configs, but never this type! I did notice that you use MiniOrange, but unfortunately their documentation did not help much.

When I go to the Keycloak page, it nicely goes to IceHRM's login-page. But login fails.

In the logs:

icehrm-1         | NOTICE: PHP message: SAML: certificate count = 1
icehrm-1         | NOTICE: PHP message: SAML: Responses  is not signed
icehrm-1         | [2025-02-10 05:34:54] IceHrm.ERROR: (client=icehrm) SAML: response signature validity : [] []
icehrm-1         | [2025-02-10 05:34:54] IceHrm.ERROR: (client=icehrm) Invalid response or assertion signature [] []
icehrm-1         | [2025-02-10 05:34:54] IceHrm.INFO: (client=icehrm) SSO SAML User Email: [] []
icehrm-1         | 2025/02/10 00:04:54 [error] 9#9: *877 FastCGI sent in stderr: "PHP message: SAML: certificate count = 1PHP message: SAML: Responses  is not signed" while reading response header from upstream, client: <redacted>

According to MiniOrgange both "Sign documents" and "Sign assertions" had to be on. I took the main X.509 from "SAML 2.0 Identity Provider Metadata", as I normally do for SAML.

I hope somebody can help me here, how to fix this.

@VincentSC
Copy link
Author

Bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant