test/jap
1
0
Fork 0
mirror of https://gitee.com/fujieid/jap.git synced 2024-12-02 11:18:53 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
9773310f7b
jap/CHANGELOGS.md
yadong.zhang 9773310f7b 📝 docs: change the CHANGELOGS.md
2021-08-15 21:42:16 +08:00

11 KiB
Raw Blame History

v1.0.4 (2021-08-**)

  • fix: [jap-ids] Support to generate custom token. (Gitee#I3U1ON)
  • fix: [jap-ids] Support custom verification of client_secret, such as: BCrypt, etc. (Gitee#I44032)
  • feat: [jap-ids] When IdsConfig#enableDynamicIssuer is true, custom context-path is supported.
  • fix: [jap-ids] Solve the problem of "After refreshing the token, the user information cannot be obtained with the new access token". (#I3XHTK)
  • feat: [jap-oauth2] Oauth2Strategy supports the following methods: refreshToken, revokeToken, getUserInfo
  • fix: [jap-social] Cannot customize JapCache and AuthStateCache of SocialStrategy at the same time. (Github#6)
  • fix: [jap-core] fix npe bug. (Github#5)
  • doc: change the template of issue and PR
  • fix: [jap-ids] 支持生成自定义 token（包含 access_token 和 refresh_token）。 (Gitee#I3U1ON)
  • fix: [jap-ids] 支持自定义验证 client_secret，适配多种场景，如：BCrypt 等。 (Gitee#I44032)
  • feat: [jap-ids] 当启用 IdsConfig#enableDynamicIssuer 时，支持自定义 context-path
  • fix: [jap-ids] 解决“刷新token后，用新的access_token无法获取用户信息”问题。 (Gitee#I3XHTK)
  • feat: [jap-oauth2] Oauth2Strategy 支持使用以下方法： refreshToken、revokeToken、getUserInfo
  • fix: [jap-social] 无法同时自定义SocialStrategy的 JapCache and AuthStateCache.(Github#6)
  • fix: [jap-core] 修复 userId 为空时 NPE 异常. (Github#5)
  • doc: 更改 issue 和 pr 的模板

v1.0.3 (2021-07-28)

  • (fix): a bug of JwkUtil
  • (fix): cannot refresh token
  • (pr): Merge Gitee PR #16 by @lowis
  • (issue): Fix Gitee #I3YWTD
  • Upgrade justauth to 1.16.2

v1.0.2 (2021-05-24)

New features

  • jap-ids

    • Add the enableDynamicIssuer in IdsConfig. When enableDynamicIssuer=true, jap ids will automatically extract issuer from the currently requested domain name.
    • Add the loginPageUrl in IdsConfig:
      • loginPageUrl: login form page url
      • loginUrl: The api url for login
    • Add the externalLoginPageUrl in IdsConfig. when the login page is not provided by an authorized service (the login page is hosted by other services), you need to enable this configuration.
    • Add the externalConfirmPageUrl in IdsConfig. When the authorization confirmation page is not provided by an authorized service (the authorization confirmation page is hosted by other services), you need to enable this configuration.
    • Add the authorizeAutoApproveUrl in IdsConfig. When the authorize url contains autoapprove=true, it will not jump to the confirmPageUrl, but will jump directly to the authorizeAutoApproveUrl.
    • Add some scopes, such as profile, address, read and write.
    • Add the uid in the OauthUtil#createAuthorizeUrl(String, IdsRequestParam).
    • Add the IdsUserStoreService interface to support custom operations on user data after login.
    • Add the IdsPipeline interface, developers can customize the process, currently only supports the process of customizing IdsxxFilter and LoginEndpoint.
    • Add SPI plugin mechanism

  • jap-social

    • SocialStrategy provides methods of refreshToken, revokeToken, and getUserInfo

Modified

  • jap

    • javax.servlet-api -> jakarta.servlet-api

  • jap-ids

    • Modify IdsConfig.confirmUrl to confirmPageUrl.
    • Modify the return value of ApprovalEndpoint#getAuthClientInfo(HttpServletRequest) to IdsResponse<String, Map<String, Object>>.
    • Modify the return value of Ap provalEndpoint#authorize(HttpServletRequest) to IdsResponse<String, String>.
    • Modify the return value of AuthorizationEndpoint#agree(HttpServletRequest) to IdsResponse<String, String>.
    • Modify the return value of LoginEndpoint#signin(HttpServletRequest) to IdsResponse<String, String>.
    • Modify the return value of LogoutEndpoint#logout(HttpServletRequest) to IdsResponse<String, String>.
    • Modify the comment content of ClientDetail.
    • Modify the return type of IdsResponse#getData() to the specified generic.
    • Remove IdsScopeProvider#initScopes(List<IdsScope>).
    • When response_type=id_token, the resulting Claims are returned in the ID Token.
    • Optimize the process of UserInfoEndpoint#getCurrentUserInfo(HttpServletRequest), Response UserInfo Claims using Scope Values.
    • Modify the loginByUsernameAndPassword and getByName methods of the IdsUserService interface, and add the clientId parameter, which can be used to distinguish multi-tenant scenarios

PR

Issue

v1.0.1（2021-04-21）

New features

  • Add com.fujieid.jap.core.util.RequestUtil
  • Complete the development of the jap-ids module, and provide oauth services externally based on jap-ids
    • Supported features：
      • Authorization Code Grant
      • Proof Key for Code Exchange
      • Implicit Grant
      • Resource Owner Password Credentials Grant
      • Client Credentials Grant
      • Refresh access token
      • Revoke access token
      • Get the currently authorized user
      • Verify login status
      • Abnormal prompt
      • Sign out
      • OpenID Connect Discovery
      • JWK Endpoint
      • Custom jwt encryption and decryption certificate
      • Support multiple response types, such as: code, token, id token, id token token, code id token, code token, code id token token
      • ...

For more details about the use of jap-ids, please refer to the sample project: jap-ids-demo, or refer to the document: IDS OAuth 2.0 服务端

Modified

  • [jap-oidc] Optimize the OidcStrategy#authenticate method, cache the OidcDiscoveryDto, and reduce unnecessary http requests
  • [jap-oidc] Optimize the code of OidcUtil, fix known bugs
  • [jap-social] fix known bugs
  • Refactor com.fujieid.jap.core.cache.JapLocalCache, implement timer manually, clean local cache regularly

PR

Issue

v1.0.1-alpha.1（2021-03-07）

Modified

  • Fix the description error in JapErrorCode
  • Improve the JapTokenHelper

PR

  • Merge Gitee PR #8

v1.0.1-alpha（2021-03-05）

jap-core

New features

  • Add JapErrorCode enumeration class to manage exception codes and exception prompts
  • Add JapResponse class to standardize interface return content
  • Add JapTokenHelper class to manage user tokens uniformly
  • Add JapContext class to maintain jap context information
  • Add JapAuthentication class, unified management of login status information and jap context information

Modified

  • Package structure
    • Move AuthenticateConfig, JapConfig to com.fujieid.jap.core.config package
    • Move JapUtil to com.fujieid.jap.core.util package
  • delete
    • Delete JapCacheContextHolder
    • Delete JapUserStoreContextHolder
  • Code
    • Refactored AbstractJapStrategy, introduced JapContext and JapAuthentication classes
    • Refactor the JapConfig class, only retain the sso and ssoConfig attributes, and add the tokenExpireTime and cacheExpireTime attributes at the same time
    • Modify the default validity period of the cache in JapCacheConfig to 7 days
    • Modify the default content in the JapUserService interface class
    • Add the void remove key( string key) method to JapCache
    • Add errorCode and errorMessage attributes in JapException to facilitate the processing of exception information into unified format return data
    • Add the token attribute to JapUser, and the jap token will be automatically returned after login
    • In the JapStrategy interface, the return type of the authenticate method is changed to JapResponse, and the strategy methods of all modules return data in a unified format
    • Mark the redirect method with @Deprecated in the JapUtil class, and it may be deleted in the future. At the same time add the createToken method

jap-oauth2

  • Modify the authenticate method of Oauth2Strategy to return JapResponse

jap-oidc

  • Modify the authenticate method of OidcStrategy to return JapResponse

jap-simple

  • Modify the authenticate method of SimpleStrategy to return JapResponse

jap-social

  • Modify the authenticate method of SocialStrategy to return JapResponse

jap-sso

  • Modify the return value of the JapSsoHelper#login method to the jap token of the current user
  • Add JapSsoUtil
  • In the japSsoConfig class, delete the login url and logout url attributes

Other

  • Add some unit tests

v1.0.0（2021-02-18）

New features

  • added jap-mfa module to realize TOTP verification
  • The logout method is added to the JapUserStoreContextHolder to support clearing cookies and sessions
  • added test cases

Modified

  • Updated jap.sh, support a variety of common commands
  • The options attribute in JapConfig is deleted, and the justathConfig attribute is added to SocialConfig
  • Change the name of RemberMeDetailsUtils to RembermeUtils
  • Move the Oauth2Strategy#checkOauthConfig() and Oauth2Strategy#isCallback() to the Oauth2Util

Other

  • Improved code
  • Reconstruct the SimpleConfig, and move the unnecessary configuration items and business logic to the RememberMeUtils

v1.0.0-alpha.1（2021-02-01）

New features

  • Add cache module com.fujieid.jap.core.cache.JapCache
  • Add 'state' verification logic in jap-oauth2
  • Add some package-info.java

Modified

  • Revision notes
  • To solve the problem that 'codeverifier' in 'pkceutil' can only be cached locally
  • Upgrade simple-json to 0.0.2

other

  • Fix Javadoc compilation failure

1.0.0-alpha（2021-01-28）

JA Plus(JAP) is an open source authentication middleware, it is highly decoupled from business code and has good modularity and flexiblity. Developers could integrate JAP into web applications effortlessly.

Completed