Auth methods
Understand what each authenticator can prove.
Each campus service has different behavior, metadata, redirects, and failure shapes. The method you choose determines what the library can verify and what information it can return.
Manual fallback
`Manual` is the default for most callers. It runs the configured sequence and stops when an authenticator returns a definite authentication result. This helps when one endpoint is down, one page changes, or one service cannot expose enough information by itself.
Use fallback when: you care more about a reliable yes/no answer than about which exact campus service produced it.
Supported methods
PortalSSOToken
Checks portal SSO token behavior through the Blackboard-related flow. It is useful when the integration only needs to know whether credentials can pass an SSO gate.
ClassicSession
Uses a session-based Daeyang Humanity College flow. It can expose profile and reading-certification details when the upstream page returns the expected structure.
MoodlerSession
Uses the LMS login flow and checks the member panel. It is useful when an application needs basic identity metadata after successful authentication.
DosejongSession
Uses a DoSejong session login and extracts account information from the service page when present.
LegacyAuth
Provides older helper-style methods such as `dosejongApi`, `uisApi`, and `sjlmsApi`. New code should prefer `AuthService` for clearer response handling.
Selection guidance
Pick the narrowest method that gives your application the required answer. If the application needs metadata, choose a method that can extract it. If the application only needs a credential decision, fallback mode is usually more resilient.
| Need | Recommended path | Why |
|---|---|---|
| Most reliable credential decision | `Manual` | Can continue when one service cannot decide. |
| SSO status only | `PortalSSOToken` | Checks the SSO-oriented flow directly. |
| Name or major metadata | `MoodlerSession` or `DosejongSession` | These flows can expose profile fields. |
| Older integration compatibility | `LegacyAuth` | Preserves historical helper methods. |