Keycloak is running locally on http://localhost:8280 with admin credentials:
adminadminhoneydipper (or any name)samlhttp://localhost:9000/api/auth/saml/callbackhttp://localhost:9000/api/auth/saml/callbackemail or persistent (if you see this field)In Keycloak, the SAML metadata is not shown in a UI field—it’s auto-generated and available at a URL. For the master realm, it’s:
http://localhost:8280/realms/master/protocol/saml/descriptor
You can verify it works by visiting that URL in your browser—it should return an XML file with the IdP metadata.
If you created a different realm, use:
http://localhost:8280/realms/{REALM_NAME}/protocol/saml/descriptor
Use this URL in your Honeydipper config’s idp_metadata_url field.
testusertestuser@example.comTestUserUpdate your sample-auth-saml.yaml:
drivers:
auth-saml:
package: builtin
type: auth-saml
config:
acs_url: "http://localhost:9000/api/auth/saml/callback"
idp_metadata_url: "http://localhost:8280/realms/master/protocol/saml/descriptor"
jwt_signing_key: "your-secret-key-for-signing-jwt"
entity_id: "honeydipper" # must match client ID in Keycloak
token_expiration: 3600
Then:
go run ./cmd/honeydipper -c <your-config>http://localhost:9000/api/auth/saml/login/api/auth/saml/callback with a SAMLResponseCheck Keycloak logs:
podman logs -f <container_name_or_id>
Common issues:
acs_url in config exactly matches what’s configured in Keycloak cliententity_id in config should match the Client ID in Keycloakemail or persistent)When done testing:
podman stop <container_name_or_id>
Or just restart your system—the --rm flag will clean it up on stop.