Buckets:
AnonymousSpottedToad/human_verified_bucket / human_annotated /mappings /java /authentication_pwd__catch-money_java-impetus.json
| { | |
| "role_mappings": [ | |
| { | |
| "role": "Subject", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "The caller is an external HTTP client that POSTs /v1/login/up; the repo only contains the request DTO (LoginRequest), not the subject itself.", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Enforcer", | |
| "symbol": "login", | |
| "file": "java-impetus-auth-impl/src/main/java/io/github/jockerCN/api/LoginApi.java", | |
| "lines": "40–124", | |
| "notes": "@RestController mapped to /v1/login exposing POST /up, the single credential entry point of the framework; it refuses to issue a token and returns 'account does not exist' / 'password is incorrect' unless the presented password matches the stored one. Enforcement of subsequent requests is token-based (DefaultFilter/TokenParseSecurityRequestFilter in the same module), which is a different pattern.", | |
| "status": "present", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Verification manager", | |
| "symbol": "login", | |
| "file": "java-impetus-auth-impl/src/main/java/io/github/jockerCN/api/LoginApi.java", | |
| "lines": "42", | |
| "notes": "Orchestrates the whole verification: obtains a Cryption instance and decrypts the submitted username/password (lines 44-50), loads the stored account via UserAccount.getByUsername (line 56), and drives the comparison at line 62 before generating a token. No separate AuthenticationProvider/UserDetailsService exists — Spring Security's formLogin is explicitly disabled in SpringSecurityConfiguration.", | |
| "status": "present", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Comparator", | |
| "symbol": "equals", | |
| "file": "java-impetus-auth-impl/src/main/java/io/github/jockerCN/api/LoginApi.java", | |
| "lines": "62", | |
| "notes": "The decision point is `if (!userAccount.getPassword().equals(password))` — a direct String comparison of the stored credential against the decrypted presented password, returning a failure Result when it does not match. No PasswordEncoder#matches is used anywhere in the repo.", | |
| "status": "external", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Hasher", | |
| "symbol": "md5", | |
| "file": "java-impetus-common/src/main/java/io/github/jockerCN/secret/CryptoUtils.java", | |
| "lines": "105", | |
| "notes": "Repo-defined hashing helper (wraps commons-codec DigestUtils.md5Hex); it is the only hash applied to a credential, used to seed the stored password at account creation (UserInfoApi.addAccountInfo line 198) and at password reset (UserInfoApi.resetPwd line 115). Caveat: the login path itself does not hash the presented password — it compares plaintext against the stored value — and UserInfoApi.changePwd (line 311) writes the new password unhashed; an unused toSHA256 also exists at line 89.", | |
| "status": "present", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Password store", | |
| "symbol": "getByUsername", | |
| "file": "java-impetus-auth-impl/src/main/java/io/github/jockerCN/api/LoginApi.java", | |
| "lines": "56", | |
| "notes": "The lookup the login path calls to fetch the stored credential by identifier; it queries the JPA @Entity UserAccount (class line 21, table user_account) whose `password` column is declared at line 42. There is no dedicated UserRepository interface — persistence goes through the generic JpaRepositoryUtils/DaoUtils helpers, so the entity's own finder is the store's access point.", | |
| "status": "present", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Encrypter", | |
| "symbol": "decrypt", | |
| "file": "java-impetus-common/src/main/java/io/github/jockerCN/secret/CryptoUtils.java", | |
| "lines": "70", | |
| "notes": "AES/ECB/PKCS7Padding (BouncyCastle) under a hard-coded 32-byte server key, reached from the login path via Cryption.getInstance(...).decryptAsString on both the username and the password (LoginApi lines 44-50); the matching encrypt primitive is at line 82. This is keyed encryption of the credential in transit, not a pepper over the stored hash — the encryption_data table (EncryptionData, with salt and algorithm_key columns) is never consulted by the verification path, so no pepper step exists.", | |
| "status": "present", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "System", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "This is a reusable Spring Boot auth starter, not an application: on a successful password check LoginApi only mints and records a token (TokenGenerate/TokenRecordProcess), and the business logic to be protected belongs to the downstream app. The in-repo admin endpoints (UserInfoApi, GroupApi, PermissionApi) are reached only in a later token-validated request, not by this login flow.", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Pepper store", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Registrar", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Resetter", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Password policy", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "Hash manager", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "", | |
| "status": "missing", | |
| "nodeId": null | |
| }, | |
| { | |
| "role": "SRNG", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "", | |
| "status": "missing", | |
| "nodeId": null | |
| } | |
| ] | |
| } | |
Xet Storage Details
- Size:
- 5.82 kB
- Xet hash:
- 3c1f552c1bbbaed856d0addd4e16088e00141b8927e3a54cac6bddd6bdbff921
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.