chenxing
|
6ceaed63d6
|
SSO 地址去掉 /cas 前缀:context-path 改为根路径,登录地址 /cas/login 变为 /login
build / build-push (push) Successful in 3m33s
|
2026-09-03 22:28:28 +08:00 |
|
chenxing
|
229067d518
|
更改登录页ico替换
build / build-push (push) Successful in 2m32s
|
2026-09-03 17:54:07 +08:00 |
|
chenxing
|
b32eb85a3c
|
更改登录页样式微调
build / build-push (push) Successful in 1m20s
|
2026-09-03 17:27:55 +08:00 |
|
chenxing
|
843b915005
|
更改登录页样式
build / build-push (push) Successful in 2m47s
|
2026-09-03 17:07:50 +08:00 |
|
chenxing
|
ced8edbbf3
|
更改登录页样式图标
build / build-push (push) Successful in 1m47s
|
2026-09-03 16:20:41 +08:00 |
|
chenxing
|
ec13cf1fb3
|
更改登录页样式图标
build / build-push (push) Failing after 33s
|
2026-09-03 16:16:01 +08:00 |
|
chenxing
|
9682d865ef
|
更改登录页样式图标
build / build-push (push) Successful in 1m29s
|
2026-09-03 15:10:34 +08:00 |
|
chenxing
|
cb2136fcdc
|
更改登录页样式
build / build-push (push) Successful in 3m11s
|
2026-09-03 14:19:23 +08:00 |
|
chenxing
|
1ba47ff6f4
|
更改登录页样式
build / build-push (push) Successful in 2m45s
|
2026-09-01 23:17:35 +08:00 |
|
chenxing
|
aa8391392c
|
更改登录页样式图片
build / build-push (push) Successful in 56s
|
2026-09-01 18:37:48 +08:00 |
|
chenxing
|
316223d096
|
更改登录页样式
build / build-push (push) Successful in 1m18s
|
2026-09-01 18:29:05 +08:00 |
|
chenxing
|
49af5d7f28
|
更改logo
build / build-push (push) Successful in 1m7s
|
2026-09-01 15:27:22 +08:00 |
|
chenxing
|
fcf9022bf0
|
修复登录按钮未绑定点击事件导致点击无反应
build / build-push (push) Failing after 43s
|
2026-08-31 22:43:30 +08:00 |
|
chenxing
|
41d7d98c77
|
静态资源更改
build / build-push (push) Successful in 44s
|
2026-08-31 22:00:07 +08:00 |
|
chenxing
|
dc8a0924a8
|
修复容器 hostname 无法解析导致的启动报错
build / build-push (push) Successful in 2m45s
现象:CAS banner 后持续 ERROR Could not determine local host name
UnknownHostException: <容器短ID>: Temporary failure in name resolution。
根因:容器 hostname 默认为容器短 ID,当前网络环境下 /etc/hosts 未含该行、
内网 DNS 亦无法解析,InetAddress.getLocalHost() 失败;连锁导致 CAS
TicketIdSanitizationUtils 静态初始化抛 ExceptionInInitializerError(票据日志带病)。
修复:ENTRYPOINT 改为 entrypoint.sh,启动前把 hostname 兜底写入 /etc/hosts
(已存在则跳过),再 exec java -jar cas.war。不依赖 projman 侧改动,任何部署方式均生效。
|
2026-08-31 20:11:11 +08:00 |
|
chenxing
|
7ff337373c
|
修复 log4j2 双版本混包导致的启动失败
build / build-push (push) Successful in 1m46s
现象:java -jar cas.war 启动即抛 NoSuchMethodError: ThreadContext.getThreadContextMap,
WAR 的 WEB-INF/lib 同时存在 log4j api/core/slf4j-impl 的 2.7 与 2.12.1 两套。
根因:spring-boot-dependencies 1.5.18 经内嵌 log4j-bom 管理 log4j 版本,默认 2.7;
BOM import 方式下 pom 覆盖 <log4j2.version> 属性不生效(属性在导入 BOM 自身上下文解析),
maven 仍解析出 2.7 全套,与 overlay war 物理自带的 2.12.1 混包,类加载顺序决定成败。
修复:dependencyManagement 最前(先声明者优先)import log4j-bom 2.12.1,
全套 log4j 钉死 2.12.1,与 overlay war 内物理版本一致,war 内仅剩单套。
|
2026-08-31 20:01:14 +08:00 |
|
chenxing
|
d6583f49f9
|
迁移 CasSsoService 源码并按 CAS war overlay 形态适配 CI
build / build-push (push) Successful in 4m8s
- 复制 CAS 5.3.16 overlay 源码(src/、pom.xml、etc/cas/config/log4j2.xml、docker/cas.properties)及本地构建辅助(build.cmd/build.sh/maven-settings.xml)
- build.yml:maven 产物由 jar 改为 war(cp cas.war app.jar),CI 内源码构建,摆脱 174MB war blob 入库
- Dockerfile:CAS 专用镜像(自签名 keystore 8443 HTTPS + 内置 cas.properties/log4j2.xml + JAVA_OPTS 注入)
- pom.xml:移除 sonatype/shibboleth 外网仓库,依赖全部经 nexus maven-public 解析
- 前端 front/ 不入库(CasSsoFront 仓库独立发布)
|
2026-08-31 18:55:29 +08:00 |
|