ARBITArkadiusz Poczobut

Identity and access

Keycloak integration with real-world environment and delivery concerns

Token handling, roles, configuration, troubleshooting, and secure service integration beyond a basic login flow.

Context

The work involved integrating or operating with Keycloak-based authentication and authorization flows where environment setup, token behavior, and permissions mapping had to align cleanly with application behavior.

Identity work requires moving between protocol concepts and practical production troubleshooting without making security someone else's problem.

Core themes

  • Identity and access management
  • SSO and token-based auth flows
  • Roles and permission mapping
  • Environment-aware configuration
  • Troubleshooting secure integrations

Technical approach

Security work grounded in application behavior

Implementation-level handling of identity concerns across backend behavior, environments, and delivery.

Handled token and session-aware flows with attention to how backend services consume identity state.
Worked through roles, permissions, and application mapping so auth behavior stayed predictable.
Treated configuration and secrets management as part of the integration rather than post-work cleanup.
Debugged issues where environment, redirects, clients, or realm setup created friction in real delivery.

Operational angle

Auth systems still need to behave across environments

Identity work overlaps with DevOps, configuration discipline, and delivery maturity.

Keycloak integration work is rarely just about implementation. It also means understanding redirect URIs, environment-specific configuration, secret handling, deployment concerns, and the kinds of subtle misalignment that turn into production issues if nobody owns them.

View skillsStart a conversation