Group: Jsentinel

Sort by:Popular▼

✓Popular✓Newest

Core authentication, authorization, and annotation-driven access contracts without Vaadin dependencies.

V00.75 SPI core for the Security Event Bus: sealed SecurityEvent hierarchy, signed SecurityEventEnvelope, EventBus API, Publish/Consume pipelines, and the SPI surfaces for SignatureAlgorithm, PayloadCodec, KeyManagement, ReplayStore, ...

Reusable test fixtures, fakes, recording sinks, and a JUnit 5 extension for projects that depend on jCustos-core. Consumers add this artifact as a test-scope dependency.

V00.72 @JCustosAutoService annotation — SOURCE retention, no runtime trace, zero project-internal dependencies. Consumed at compile time by jCustos-autoservice-processor.

V00.72 developer-experience core: common fluent-bootstrap contracts, JCustosRuntime, diagnostics (JCustosDiagnostics + DiagnosticContributor SPI). Adapter-specific bootstrap facades live in jCustos-dx-vaadin / -rest / -standalone.

V00.78 opt-in module: OpenID Connect Relying-Party identity on top of the V00.76 JWT and V00.77 OAuth2 building blocks — discovery, ID-token validation (nonce / azp / at_hash / auth_time / acr), UserInfo, RP-initiated logout and ...

V00.75 contract test suites (JUnit-5 @Test default interfaces) for the seven Security Event Bus SPIs: PayloadCodec, SignatureAlgorithm, KeyManagement, ReplayStore, SequenceStore, ProducerPolicy, EventStore. Persistence-tech-agnostic — ...

V00.76 opt-in module: Nimbus JOSE+JWT-backed default implementation of the jCustos-core JWT SPIs (JwtValidator, JwksClient, JwtValidatorFactory) plus the JwtDiagnosticContributor. Framework-neutral — no Vaadin, no REST framework.

V00.77 opt-in module: OAuth2 Relying-Party HTTP flows — authorization-code (+ PKCE), token endpoint with client authentication (basic / post / secret-jwt / private-key-jwt / none), refresh-token rotation with reuse-detection, revocation, ...

Framework-light REST adapter for jCustos-core.

Vaadin Flow adapter for the jCustos-core module.

V00.74 declarative token-propagation runtime: PropagatingProxy runtime path, PropagationDiagnosticContributor, and the PropagateTokenAdvisor.Default wiring consumers depend on. The matching compile-time wrapper lives in ...

V00.80.00 (Konzept goal 7) forensic audit: AuditChainStore hash-chaining, AuditIntegrityVerifier, SignedAuditBatch and verifiable exports on top of the persistent audit from V00.70. Complements, does not replace, the EventBus signature layer.

Eclipse-Store-backed implementations of every Phase-2 persistence store (AuditEvent, Session, LoginAttempt, RoleAssignment, BootstrapState, RememberMe / PasswordReset / EmailVerification tokens, ApiKey, RefreshToken, RateLimit). Each ...

V00.80.00 (Konzept goal 7) contract test suite for the AuditChainStore SPI plus correctly-hashed chain fixtures. Persistence-tech-agnostic: every store implementation runs the same @Test-default contract.

Optional Phase-1b extension that adds memory-hard and bcrypt-style password hashing providers backed by BouncyCastle (Argon2id, bcrypt, scrypt) on top of the V00.71 PasswordHashProvider SPI from jCustos-core. Strictly opt-in: applications ...

V00.72 Vaadin-specific fluent bootstrap: VaadinSecurity.bootstrap() facade and the VaadinJCustosBootstrap builder. Hosts the VaadinDiagnosticContributor (added in Prompt 014a).

V00.77 opt-in module: REST-side OAuth2 RP glue — the authorization-code callback RestHandler and the JDK in-memory StateStore default.

V00.77 opt-in module: Vaadin-side OAuth2 RP glue — the standardized authorization-code callback route and the VaadinSession-backed StateStore.

JUnit-5 contract interfaces that every concrete implementation of the Phase-2 persistence stores must satisfy. Consumers (the in-memory defaults and the Eclipse-Store-backed implementations alike) write one tiny adapter class per store ...