CACampus Auth Java

Documentation

Campus authentication workflows, wrapped in a small Java toolkit.

Campus Auth Java provides a CLI and library API for authorized campus-account verification experiments. It hides the repetitive parts of session login flows, cookies, redirects, HTML parsing, fallback behavior, and JSON formatting behind predictable Java interfaces.

Start buildingRead the API guide

Mental model

The library is built around a simple question: did an authorized credential check produce a trustworthy authentication result? Real campus services do not always answer that cleanly. A network timeout, redirected login form, changed HTML structure, or unavailable endpoint should not be treated the same as a wrong password.

Campus Auth Java separates those outcomes. Each authenticator reports whether the service interaction succeeded, whether authentication was confirmed, which status code or result code was observed, and which metadata was extracted.

Service outcome

`success` tells you whether the request flow produced a usable response. It is not the same thing as authentication success.

Authentication outcome

`is_auth` is the credential result when known. It can be `null` when the endpoint cannot give a definite answer.

Fallback sequence

Manual mode tries authenticators in order and stops when a method returns a definite result.

Metadata extraction

Some methods can extract account metadata such as name, major, or certification details when the upstream page exposes it.

A complete CLI response

The CLI prints JSON so scripts, club tools, and prototypes can consume the output without parsing terminal text. The exact metadata depends on the method that succeeds.

Shell
java -jar target/campus-auth-java-0.2.7.jar student_id
Password:
{
  "success": true,
  "is_auth": true,
  "status_code": 200,
  "code": "success",
  "authenticator": "DosejongSession",
  "body": {
    "name": "Example Student",
    "major": "Computer Science"
  }
}

Build paths

Use the CLI

Build the shaded jar and run fallback or selected authenticator checks from the terminal.

Embed in Java

Call `AuthService` directly from another Java application and handle structured response objects.

Choose a method

Understand what each authenticator checks, what it can extract, and when fallback is safer.

Operate safely

Review authorization requirements, credential handling, disclosure policy, and misuse boundaries.
Next: Quickstart