WSO2 Identity Server 7.0.0 RC4

We are pleased to announce the fourth release candidate of WSO2 Identity Server 7.0.0.

What is new in this release

WSO2 Identity Server 7.0.0 is the latest WSO2 Identity Server release and is the successor of WSO2 Identity Server 6.1.0. It contains the following new features and enhancements:

New Features

• Refreshing look and feel for the console UI
  The console just got a major upgrade with our brand-new, lightning-fast Oxygen UI to be consistent with the experience of Asgardeo UI! Beta console UI (accessible via /console) introduced in the 5.11.0 version is now available for production usage for administrative and developer tasks.

  With this upgrade concepts like service providers, identity providers, and inbound/outbound authentication that have been used in the carbon-based management console have changed to ‘applications’ and ‘connections’ respectively. Identity Server 7.0.0 includes application templates for SPA, web applications with server-side rendering, mobile applications, and M2M applications along with various authentication options to pick and choose from connections that include social login, MFA, passwordless, etc.

• Productized support for B2B CIAM use cases
  Identity Server now enables secure access for your B2B business customers with flexible organization management capabilities. B2B CIAM is the identity foundation that helps organizations that work with business customers, franchises, distributors and suppliers get their apps and services to market quickly and securely.

• Authentication API that facilitates implementing app-native authentication
  When developing applications (especially native/mobile apps) developers look at implementing their login flows within the apps themselves where they target more UX.

  To cater to this requirement, API-based authentication capability is introduced which will provide the app developer the capability to implement a complete authentication capability within the application.

• OAuth 2.0 specifications
  Identity Server now supports following OAuth 2.0 specifications designed to protect APIs exposing high-value and sensitive (personal and other) data.

  • JWT Secured Authorization Response Mode
  • Pushed Authorization Requests

• Compliant with FAPI 1.0 Baseline and Advanced profiles

• First-class support for securing API resources
  Identity Server now offers comprehensive support for the API Authorization via RBAC.

• Command line utility to manage Identity Server configurations in CI/CD workflows

• FIPS 140-2 Compliance

• HYPR for passwordless and biometric authentication
  Identity Server now provides the HYPR connector as an authentication option for the applications.

Enhanced Features

• Branding and i18n support for end-user facing UIs and email templates
• Email and SMS OTP for passwordless login
• Idle account identification API
• Client-Id as an input parameter to perform OIDC RP-Initiated logout
• Use a different browser to open the email magic link and log in to the app

Deprecated features

Refer to the about this release section in the product documentation to find the deprecated from WSO2 IS 7.0.0 onwards. These features will be removed in a future release and we expect you to move to recommended solutions.

Fixes and Improvements

See the complete list of issues fixed in the latest WSO2 IS 7.0.0 release.

Documentation

The product documentation for this version is available at https://is.docs.wso2.com/en/7.0.0

Contribute to WSO2 Identity Server

Mailing Lists
Join our mailing lists and correspond with the developers directly. We also encourage you to take part in discussions related to the product in the architecture mailing list. If you have any questions regarding the product you can use our StackOverflow forum to raise them as well.

Developer List: [email protected]
Architecture List: [email protected]
User Forum: StackOverflow

Reporting Issues

We encourage you to report issues, improvements, and feature requests regarding WSO2 Identity Server through our public WSO2 Identity Server GIT Issues.

Important: And please be advised that security issues must be reported to [email protected], not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.

~ The WSO2 Identity and Access Management Team ~