shimingxy
|
9f697437a8
|
remove provision
|
2026-01-06 09:39:39 +08:00 |
|
shimingxy
|
b4c95363e1
|
Surpass
|
2025-12-31 10:45:28 +08:00 |
|
shimingxy
|
f5eebc195d
|
代码优化
|
2025-12-26 10:35:26 +08:00 |
|
MaxKeyTop
|
acafd86829
|
!69 update README.md.
Merge pull request !69 from smxzk32145745/N/A
|
2025-12-26 01:07:36 +00:00 |
|
MaxKeyTop
|
42dacf24e4
|
!68 update NOTICE.
Merge pull request !68 from smxzk32145745/N/A
|
2025-12-26 01:03:30 +00:00 |
|
smxzk32145745
|
eb6419020f
|
update README.md.
Signed-off-by: smxzk32145745 <smxzk32145745@163.com>
|
2025-12-25 07:58:27 +00:00 |
|
smxzk32145745
|
1e1f20e370
|
update NOTICE.
术语大小写不规范:
"IDaas" 应该是 "IDaaS" (Identity as a Service 的标准缩写)
"OPENID CONNECT" 应改为 "OpenID Connect" (专有名词规范大小写)
"Single Sign On" 应改为 "Single Sign-On" (标准术语带连字符)
英文部分语法问题:
"Maxkey" 大小写不一致,应统一为 "MaxKey"
"Support OAuth" 应改为 "Supports OAuth" (主谓一致)
"Provide Secure" 应改为 "Provides secure" (主谓一致,大小写规范)
"Access management (AM)" 应改为 "Access Management (AM)" (M大写)
"Identity management (IDM)" 应改为 "Identity Management (IDM)"
格式问题:
"Secure , Standard" 逗号前后有不必要空格
版权声明缺少版权符号和年份,应为 "Copyright © [年份] http://www.maxkey.top All Rights Reserved."
技术术语规范:
"IAM-IDaas Identity and Access management Product" 表述不够专业,应调整为 "a leading-edge IAM/IDaaS (Identity and Access Management) product"
Signed-off-by: smxzk32145745 <smxzk32145745@163.com>
|
2025-12-25 07:43:21 +00:00 |
|
shimingxy
|
ebe1001f20
|
Unnecessary path variable definition [WEB_ANNOTATION_NAMES]
|
2025-12-22 14:23:46 +08:00 |
|
shimingxy
|
424a86d3e7
|
Unnecessary path variable definition [WEB_ANNOTATION_NAMES]
|
2025-12-22 12:15:39 +08:00 |
|
shimingxy
|
83699f1b86
|
Update RestTimeBasedOtpController.java
|
2025-12-22 12:06:35 +08:00 |
|
shimingxy
|
f699845378
|
remove build_docker.gradle
|
2025-12-22 11:55:12 +08:00 |
|
shimingxy
|
90071168df
|
README
4.1.10
|
2025-12-12 09:27:06 +08:00 |
|
shimingxy
|
ff641f8b65
|
v 4.1.10 ReleaseNotes
|
2025-12-12 09:23:02 +08:00 |
|
shimingxy
|
39a1a260ba
|
org.gradle.caching =true
|
2025-12-12 09:11:14 +08:00 |
|
shimingxy
|
5119a64364
|
gradle repositories
|
2025-12-11 18:33:56 +08:00 |
|
MaxKey
|
bb7109bbfc
|
Update environment.ts
|
2025-12-10 20:49:51 +08:00 |
|
MaxKey
|
56dc9eba1c
|
v 4.1.10 README
|
2025-12-10 20:47:00 +08:00 |
|
MaxKey
|
178635c410
|
sql v4.1.10
|
2025-12-10 20:24:45 +08:00 |
|
shimingxy
|
f121350ed9
|
Update README.md
|
2025-12-10 18:14:48 +08:00 |
|
shimingxy
|
1755969cfa
|
Update README.md
|
2025-12-10 18:13:45 +08:00 |
|
shimingxy
|
ba5b0a4911
|
sql\README.md
|
2025-12-10 18:12:13 +08:00 |
|
shimingxy
|
499deff645
|
swagger依赖升级
|
2025-12-10 15:48:56 +08:00 |
|
shimingxy
|
b7a2c9fe15
|
4.1.10 GA
|
2025-12-10 10:59:19 +08:00 |
|
shimingxy
|
8f987290b9
|
eclipse jdt settings
|
2025-12-10 10:27:48 +08:00 |
|
shimingxy
|
ac98b93dbf
|
Merge branch 'main' of https://github.com/dromara/MaxKey
|
2025-12-08 17:50:47 +08:00 |
|
shimingxy
|
c5d71fbb36
|
actuator and /swagger-ui 安全性增强
"/actuator","/actuator/**","/swagger-ui","/swagger-ui/**"
|
2025-12-08 17:49:29 +08:00 |
|
MaxKey
|
8543ce9406
|
sql olderVersions
|
2025-12-06 10:52:03 +08:00 |
|
shimingxy
|
e71e4c068f
|
新建 org.dromara.maxkey.id
uuid
SnowFlakeId
IdTimeSequence
|
2025-12-04 10:59:13 +08:00 |
|
shimingxy
|
ea2a012617
|
Merge branch 'main' of https://github.com/dromara/MaxKey
|
2025-12-04 09:28:34 +08:00 |
|
MaxKey
|
cf9e66ca3f
|
默认关闭 actuator,消除actuator 未授权访问漏洞
|
2025-12-03 20:22:06 +08:00 |
|
MaxKey
|
ff9a199e4f
|
maxkey-starter-web-static
|
2025-12-03 20:13:00 +08:00 |
|
MaxKey
|
7f5e63e28b
|
freemarker use slf4j
|
2025-12-03 20:12:35 +08:00 |
|
shimingxy
|
fbc735b93d
|
RequestTokenUtils move to org.dromara.maxkey.http
|
2025-11-24 17:20:03 +08:00 |
|
shimingxy
|
62ea99f99e
|
Update IdTimeSequence.java
|
2025-11-24 17:19:34 +08:00 |
|
shimingxy
|
2e709e7352
|
springBootVersion =3.4.12
|
2025-11-24 17:12:53 +08:00 |
|
shimingxy
|
66a8569f44
|
OneTimePasswordAutoConfiguration
|
2025-11-24 17:12:43 +08:00 |
|
shimingxy
|
cfb09a2f1a
|
Gradle 9.1.0
|
2025-11-21 11:22:24 +08:00 |
|
shimingxy
|
d068d7bc2b
|
package controller
|
2025-11-21 09:01:38 +08:00 |
|
shimingxy
|
db9fa69265
|
mybatisjpaextra 3.3.8
|
2025-11-18 09:45:21 +08:00 |
|
shimingxy
|
e9b8218a6b
|
Merge branch 'main' of https://github.com/dromara/MaxKey
|
2025-11-17 17:34:14 +08:00 |
|
shimingxy
|
0f10b9975e
|
cas Response & druid & org.dromara.maxkey.http
|
2025-11-17 17:33:32 +08:00 |
|
MaxKey
|
87a4c936e1
|
Merge pull request #261 from link2fun/fix-generate-secret-cannot-refill-form
修复 编辑应用 生成应用密钥无法自动回填
|
2025-11-07 15:52:57 +08:00 |
|
link2fun
|
ef2b40cdb6
|
修复 编辑应用 生成应用密钥无法自动回填
|
2025-11-07 13:40:09 +08:00 |
|
MaxKey
|
9f8b5b9d1b
|
Merge pull request #260 from link2fun/fix-weixinwork-sync-issue
完善企业微信同步器同步 同步组织和用户覆盖更多场景
|
2025-11-07 08:32:47 +08:00 |
|
link2fun
|
ee4d52e65a
|
企业微信用户同步 增加自动禁用离职用户账号
|
2025-11-06 19:30:58 +08:00 |
|
link2fun
|
f92c0032a7
|
对企业微信用户同步进行一些场景判断 , 大致应该是分成了4种情况
1. 有同步记录, 用户存在 -> 更新用户信息
2. 有同步记录, 用户不存在 -> 重新创建用户 使用原本的用户Id
3. 无同步记录, 用户存在 -> 说明是手工创建的用户, 手动创建的用户应当是不能直接关联, 因为无法确认 这个用户和企业微信同步过来的用户是同一个人
4. 无同步记录, 用户不存在 -> 正常创建用户
|
2025-11-06 15:54:22 +08:00 |
|
shimingxy
|
d6ac702b4c
|
mybatis-jpa-extra 3.3.7
|
2025-11-06 09:13:49 +08:00 |
|
shimingxy
|
9e5bf6e5b3
|
商业数据库驱动需手动引入
|
2025-11-06 09:12:34 +08:00 |
|
link2fun
|
38ea7b7b60
|
代码整理
|
2025-11-05 17:23:53 +08:00 |
|
link2fun
|
bc54cb256c
|
完善企业微信同步器同步,修正 已同步的组织被删除后 后续同步无法恢复
|
2025-11-05 17:01:49 +08:00 |
|