This documentation is intended for Crowd developers who want to ensure that their existing apps are compatible with Crowd 6.2.

概要

Here you can find information about the latest EAP.

変更の概要

In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your apps. Once they're ready, we'll indicate when a change has been implemented.

In Crowd 6.2.0, we introduce new functionalities and features without any expected breaking changes.

2 段階認証による新しいログイン エクスペリエンス

Status: IMPLEMENTED (EAP 02)

To improve the security of the Crowd login experience, we’ve added a second authentication layer. The new login process supports a native two-step verification (2SV) capability using a time-based one-time password (TOTP) generated by an authentication app as a second factor. Explore how to manage two-step verification

If you experience any issues with the new login process during end-to-end build tests or CI/CD of your app, you can switch to the legacy login experience by setting the JVM system property -Datlassian.authentication.legacy.mode to true.

User access log

Status: IMPLEMENTED (EAP 01)

The user access log functionality stores the requests received by the Crowd application in the "logs" directory for Tomcat. By default, it’s <crowd-install>/apache-tomcat/logs. The access log is generated with the use of Tomcat valve.

With Crowd 6.2, the functionality is enabled by default and set in the Engine element of Crowd's server.xml file. By default, the configuration file is located at <crowd-install>/apache-tomcat/conf/server.xml.

Improved date format of user attributes

Status: IMPLEMENTED (EAP 01)

User attributes such as lastActive store date information in the epoch format. We’ve updated it with an additional timestamp representation displayed below the user attribute input. The displayed value represents the epoch value and regenerates on change.