Package com.svenruppert.jsentinel.audit
package com.svenruppert.jsentinel.audit
-
ClassDescriptionAccess to a protected route or endpoint was refused.A subject was granted access to a protected route or endpoint.A guarded action call was denied — the subject did not satisfy the required
ActionPermission.Emitted when an API-key authentication was refused — unknown key, expired, revoked, or in a foreign tenant.Emitted when an API-key was successfully used to authenticate a request — i.e.Persisted form of anAuditEvent.Sealed root of the typed security audit event hierarchy.Persistent counterpart toAuditSink.Filter passed toJSentinelAuditService.query(...).Write-only destination forAuditEvents.The first administrator was successfully created via the bootstrap flow.A bootstrap-token submission was rejected.The login attempt policy locked a username/client because it crossed a failure threshold.JSentinelAuditServicethat fans every published event out to: a primaryRingBufferAuditSinkused as the query backend, and zero or more additionalAuditSinks (logging, file, SIEM, …). Every sink runs independently — a failing extra sink does not stop the fan-out and never causespublish(...)to throw.A successful verification triggered a transparent rehash of the stored credential.Credential lifecycle status transitioned fromfromStatustotoStatus.Failed password verification, carrying the internal differentiated classification so audit sinks can distinguish unknown user from wrong password, broken envelope, missing provider or rejected pepper key.Successful password verification, recorded by the credential audit publisher so audit sinks see the same outcome theLoginAttemptPolicyrecorded.No-argJSentinelAuditServicesuitable forMETA-INF/servicesregistration.Emitted when an email-verification token is issued for a subject / email pair.Emitted when an email-verification token is consumed and the email is considered verified.In-memoryAuditEventStorebacked by a single tenant-scoped list.Read/write facade for security audit events.A login attempt was rejected — credentials wrong, account unknown, or blocked by an upstream policy.Credentials were accepted and the subject is now authenticated.A subject's session was terminated by an explicit logout.DefaultJSentinelAuditService— discards every event and never retains anything.Emitted when a password-reset token is consumed and the password has been replaced.Emitted when a password-reset token is issued for a subject.A namedPolicywas evaluated against aPolicyContext.Emitted byRateLimitPolicy.tryAcquirewhen an event was refused because the per-key event count within the configured window equals or exceeds the limit.Bounded in-memory ring buffer ofAuditEvents.A role was assigned to a subject by an administrator action.A role was revoked from a subject by an administrator action.A new session was opened for a subject (typically after successful login).A session was ended by the policy because it crossed an inactivity or absolute-lifetime threshold.A session was forcibly invalidated by application or framework code (rotation after login, role change, password reset, admin action).Emitted when a request was refused because the session's security-version snapshot no longer matches the subject's current version.An adapter challenged the subject for a step-up authentication — either via an HTTP401 + WWW-Authenticateresponse (REST) or by rerouting to a configured step-up route (Vaadin).JSentinelAuditServicethat persists events through anAuditEventStore(Phase 2).Emitted when a refresh-token rotation succeeded — the old token was consumed and a fresh access + refresh pair was issued.A new user account was added to the directory.A user account was removed from the directory.