Configuration

Everything is optional. If the defaults are fine, configure nothing.

Settings

Setting	Type	Default	Meaning
Request timeout	number (seconds)	10	Connect and read timeout. Java sejongpeia.timeout-seconds, Python timeout_seconds, Node.js timeoutSeconds
Portal login retries	number	3	Java sejongpeia.max-retry, Python max_retry, Node.js maxRetry
Certificate verification	boolean	true	Java sejongpeia.ssl-verification, Python ssl_verification, Node.js sslVerification

Scope of retries

• Retries apply to the portal login request only. It is tried again on a non-2xx answer or a timeout.
• A timeout on the last attempt is CONNECTION_TIMEOUT; running out of attempts is CONNECTION_FAILED.
• A login the portal rejected for a wrong password or a lock is never retried, to protect the account.

Certificate verification

On by default. There is an option to turn it off, but treat it as a debugging tool: with it off, the connection that carries the login is not verified.

Java: without Spring

Spring Boot is an optional dependency, so a plain Java project does not pull it in. Wire the objects yourself.

import kr.suhsaechan.sejongpeia.auth.client.SejongPortalClient;
import kr.suhsaechan.sejongpeia.auth.client.SejongSisClient;
import kr.suhsaechan.sejongpeia.auth.model.SejongAuthResult;
import kr.suhsaechan.sejongpeia.auth.parser.SejongClassicReadingParser;
import kr.suhsaechan.sejongpeia.auth.parser.SejongSisParser;
import kr.suhsaechan.sejongpeia.auth.parser.SejongStudentInfoParser;
import kr.suhsaechan.sejongpeia.auth.service.SuhSejongAuthEngine;
import kr.suhsaechan.sejongpeia.common.config.SejongAuthProperties;
import kr.suhsaechan.sejongpeia.common.util.SejongTlsSupport;

SejongTlsSupport.ensureLegacyCipherEnabled();   // first thing in main(), before any other HTTPS call
SejongAuthProperties properties = new SejongAuthProperties();
SuhSejongAuthEngine engine = new SuhSejongAuthEngine(new SejongPortalClient(properties), new SejongStudentInfoParser(),
    new SejongClassicReadingParser(), new SejongSisClient(properties), new SejongSisParser());
SejongAuthResult result = engine.authenticate(studentId, password);

Java TLS caveat

The portal offers only a cipher (TLS_RSA_WITH_AES_256_CBC_SHA) that current JDKs disable. The library removes TLS_RSA_* from jdk.tls.disabledAlgorithms. That setting applies to the whole JVM and only works before the JVM’s first TLS connection.

• Spring Boot handles it automatically at startup.
• Without Spring, call SejongTlsSupport.ensureLegacyCipherEnabled() first in main(). Calling it too late fails with CONNECTION_FAILED and a message that names the cause.
• If a JVM-wide change is not acceptable, run authentication in a separate process.
• Python and Node.js change the TLS settings of their own connections only.

Background is in Legacy TLS.

Public data client

Settings of the public school data client (SejongPublicData) such as cache time, failure memory time and maximum cache entries are in Common rules.

Example code

Java

sejongpeia:
  timeout-seconds: 10     # request timeout (default 10)
  max-retry: 3            # portal login retries (default 3)
  ssl-verification: true  # portal certificate check (default true)

Python

from sejongpeia import SejongAuthClient

# create your own client only when you need non-default settings
client = SejongAuthClient(timeout_seconds=10, max_retry=3, ssl_verification=True)
result = client.authenticate(student_id, password)

Node.js

import { SejongAuthClient } from 'pro-sejongpeia';

// create your own client only when you need non-default settings
const client = new SejongAuthClient({ timeoutSeconds: 10, maxRetry: 3, sslVerification: true });
const result = await client.authenticate(studentId, password);