{"id":183899,"date":"2026-10-15T17:01:27","date_gmt":"2026-10-15T15:01:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/vypusk-issuerd-0-1-17-keycloak-sovmestimogo-servera-upravleniya-identifikacziej-i-dostupom"},"modified":"2026-10-15T17:01:34","modified_gmt":"2026-10-15T15:01:34","slug":"issuerd-0-1-17-released-a-keycloak-compatible-identity-and-access-management-server","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/issuerd-0-1-17-released-a-keycloak-compatible-identity-and-access-management-server","title":{"rendered":"Release of Issuerd 0.1.17, a Keycloak-compatible identity and access management server.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of Issuerd 0.1.17 has been published \u2014 an identity and access management (IAM) server implementing OpenID Connect and OAuth 2.x protocols, compatible with the Keycloak platform at the data model level and managing REST API. Features include SSO, MFA (TOTP, WebAuthn\/passkeys), user federation from LDAP and Kerberos\/SPNEGO, login through external identity providers (OIDC, social networks), customizable login pages with localization options, and a declarative initial configuration from YAML upon first launch. The server is written in Rust (unsafe code is prohibited at the attribute level), distributed under the Apache 2.0 license, and supplied as a single self-contained binary file that includes an administrative console and user console. Builds are created for Linux, Windows, and macOS platforms (amd64 and \narm64).<\/p>\n
The key feature of the project \u2014 continuous compliance checking \nagainst the official OpenID Foundation Conformance Suite (5.3.2). Testing is conducted in CI for each release in an isolated Docker environment. Modular results are stored in the repository, and a complete report package is attached to \neach release. Parity with Keycloak is maintained through a test suite. Plans include obtaining official certification.<\/p>\n
Among the protocols demanded in AI-agent scenarios, DPoP (RFC 9449, binding token to presentation key), token exchange (RFC 8693, narrowing permissions during token exchange), and CIBA (poll mode, human action confirmation) have been implemented. Also supported are PAR (RFC 9126), JAR (RFC 9101), JARM, RAR (RFC 9396), dynamic client registration (RFC 7591\/7592), and device authorization (RFC 8628). Importing 100,000 users from MS Active Directory takes about 30 seconds. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"