cancel
Showing results for 
Search instead for 
Did you mean: 
apleach
Content Contributor
Content Contributor

At Hyland, we regularly assess our product offerings to ensure they serve customer needs, meet industry requirements and align with our market focus. After review and with the upcoming release of Alfresco Content Services (ACS) 23.1* in Q4 2023, Hyland has chosen to begin the retirement process for Alfresco Identity Service (IDS). The end-of-life date is Sunday, September 1, 2024. More information is shared below.

 

Replacement option

Moving forward, we suggest customers use the original Keycloak project, a mature open-source project backed by Red Hat. Currently, Alfresco IDS is a thin customized layer on top of Keycloak. Because of this, customers will not lose capabilities when transitioning from Alfresco IDS to Keycloak and the user experience will not be disruptive for existing customers.

Compatible and supported versions of Keycloak will be listed in the official documentation compatibility matrix.

 

Support information

The recent release of Alfresco IDS 2.0 on Monday, August 14, helps close the gap between Alfresco IDS v1.8 and the latest Keycloak distributions, making Alfresco IDS 2.0 a possible intermediate step if required. Alfresco IDS 2.0 will be supported for one year, but Hyland will not continue the evolution or modernization of the product during this time. Because of this, using the original Keycloak project is the suggested path for customers. 

Customers can continue to contact Hyland support or their technical account manager to discuss Alfresco Identity and Access Management (IAM).

 

Helpful resources

Contact Hyland support or your technical account manager with questions about this upcoming end-of-life announcement.

 

*Based on customer feedback, we are simplifying version naming to minimize confusion and employ industry best practices. Hyland will use the new format of product name, year and version number (product name YY.#) for product and solution releases moving forward. More information is available in the naming convention Hyland Community blog post.

5 Comments