Skip to content
Skills Library
Security · Review & audit

review-auth

/review-auth

Authentication and connectivity lens of a legend-engine impact review: static analysis of changes to pac4j/identity derivation, credential providers and vaults, relational JDBC connectivity (ConnectionManagerSelector, DataSourceSpecification keys, ConnectionStateManager pool naming, AuthenticationStrategy implementations, authentication flows), other identity-bearing stores and server/session config, producing severity-ranked findings with file:line evidence. Use when a change touches Identity, Subject/doAs, credentials, vault lookups, connection pools, authentication strategies or flows, pac4

Author
finos ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Authentication and connectivity lens of a legend-engine impact review: static analysis of changes to pac4j/identity derivation, credential providers and vaults, relational JDBC connectivity (ConnectionManagerSelector, DataSourceSpecification keys, ConnectionStateManager pool naming, AuthenticationStrategy implementations, authentication flows), other identity-bearing stores and server/session config, producing severity-ranked findings with file:line evidence. Use when a change touches Identity, Subject/doAs, credentials, vault lookups, connection pools, authentication strategies or flows, pac4

Original author description

Authentication and connectivity lens of a legend-engine impact review: static analysis of changes to pac4j/identity derivation, credential providers and vaults, relational JDBC connectivity (ConnectionManagerSelector, DataSourceSpecification keys, ConnectionStateManager pool naming, AuthenticationStrategy implementations, authentication flows), other identity-bearing stores and server/session config, producing severity-ranked findings with file:line evidence. Use when a change touches Identity, Subject/doAs, credentials, vault lookups, connection pools, authentication strategies or flows, pac4

How it works

  1. Procedure
Original SKILL.md headings · 30 lines, 288 words
SKILL.md preview
---
name: review-auth
description: "Authentication and connectivity lens of a legend-engine impact review: static analysis of changes to pac4j/identity derivation, credential providers and vaults, relational JDBC connectivity (ConnectionManagerSelector, DataSourceSpecification keys, ConnectionStateManager pool naming, AuthenticationStrategy implementations, authentication flows), other identity-bearing stores and server/session config, producing severity-ranked findings with file:line evidence. Use when a change touches Identity, Subject/doAs, credentials, vault lookups, connection pools, authentication strategies or flows, pac4j config, or new HTTP endpoints, or when asked whether a change is safe from an auth or security standpoint."
---

# Auth and connectivity lens

This lens is static. EMIT runs against H2 with `DefaultH2` auth, so it cannot observe identity
behaviour. The output is a list of findings, each with evidence.

## Procedure

1. **Collect the hunks.** `engine-review scope --base <base> --head <head>` lists the files in the
   auth lens. A file matched on content ("changed lines mention Credential, doAs") counts too. Read
   each hunk with enough surrounding code to know which identity is in scope: the request's, the
   pool's, or the service's.
2. **Read `references/auth-checklist.md`** in full the first time. It explains how identity flows
   from pac4j to the JDBC pool, and why the pool name is the isolation boundary.
3. **Apply checklist sections A–H** to every hunk. Answer each applicable question with evidence
   (`file:line` and the code), not with an impression. Mark sections that do not apply as N/A in the
   review so readers can see they were considered.
4. **Trace beyond the hunk.** For a changed method, find its callers. A harmless-looking change to
   `Identity.getName()`, a key's `equals`, or a credential's `id()` propagates into pool naming,
   caches and `authId`. Follow it to where the value is consumed.
5. **Separate new from existing.** If the risky pattern already exists on base, say so. The PR may
   extend it, or merely sit next to it. Pre-existing issues go in a separate "existing risk"
   section, not in the PR's findings.
6. **Ask for tests where the checklist names one** (pool separation per user, fail-closed on a
   credential error, no secrets in logs, endpoint authorization) and none exists.
7. **Severity** follows the checklist: blocker, major or minor.

Never paste a secret, token or real credential value into the review. Describe where it would leak,
not what it is.

Versions

The database has no other skills named review-auth.

Database snapshot: 13.11.2026 · package version 417753ad98e4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100review-impact
    Targeted impact review of a legend-engine change (PR number, branch, commit range, or uncommitted work) for reviewers and authors: classifies the diff into hot-area lenses (SQL generation, protocol JSON, auth/JDBC connectivity), runs the EMIT corpus on base and head to show how…
  • 100validating-authentication-implementations
    Validate authentication mechanisms for security weaknesses and compliance. Use when reviewing login systems or auth flows. Trigger with 'validate authentication', 'check auth security', or 'review login'.
  • 100validating-authentication-implementations
    Validate authentication mechanisms for security weaknesses and compliance. Use when reviewing login systems or auth flows. Trigger with 'validate authentication', 'check auth security', or 'review login'.
  • 100authentication-patterns
    Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.