Project FAQ censhare and Keycloak

censhare 2022 with Keycloak bring about some important changes regarding installation, configuration and development.

It is therefore mandatory that you make yourself familiar with the product and developer documentation and tutorials before you start to upgrade or install to censhare releases as of 2022.1:

Read the following chapters:

• Technical FAQ censhare and Keycloak
• Installation 

You also need knowledge about Keycloak as some configurations and customization are moved to Keycloak and can only be carried out in Keycloak.

• Authentication and user management
• Keycloak documentation by Keycloak
• Curated list of resources for learning about http://www.keycloak.org

Frontend customization censhare Web

Partner login required to access instructions.

• Customization updates: If the project has its own customization in form of additional frontend code (placed in the censhare-Custom folder), and for any locale that is used, you need to properly build and deploy the extensions. See Release frontend bundles and Build, release, deploy frontend bundles. This can be prepared in a local Dev environment. See Getting started censhare. 
• Customization workflow: Developing censhare custom solutions now involves additional steps. You have to set up a DevOps environment that allows you to track, merge, test, stage and deploy the desired scope of changes. Customizations involved building, releasing, and deploying weppacked frontend bundles. See DevOps environment and Build, release, deploy frontend bundles.
• Branding: The dynamic branding with a  Branding asset that is assigned in the  System asset no longer work. The  Branding asset is deprecated. If you upgrade your branded censhare from an earlier version below 2021.2, you must implement the new branding. Your old branding will not work anymore. See Custom branding.

Every software update means changes in the database schemas. Those changes are a bit tricky to revert. This can only be done by applying SQL statements that revert the previous database migration also done by means of SQL statements and/or migration scripts. 

However, in a normal case, you should have a dry run of the system before you start generating any new data. Once you notice that you need a downgrade, you can deinstall the new version and install the previous one as well as use the latest database backup. Indeed, this mean that you need to prepare such backup in advance. 

As already mentioned, censhare WP includes additional software components as compared to censhare Classic. It may require an upgrade in the hardware you are using. Consequently, there can be a certain increase in your infrastructure costs. 

Please consult your censhare partner or partner account manager. If you are hosting your censhare system in a third-party cloud, you may need to involve your provider in the new cost calculation. 

For understandable reasons, we cannot provide 2nd or 3rd level support for Keycloak. Our support services are limited to the integration of Keycloak with censhare. As Keycloak is a third-party tool, we cannot influence or change how Keycloak behaves. 

Keycloak is an open-source software product to allow single sign-on with Identity and Access Management aimed at modern applications and services. The open-source project is under the stewardship of Red Hat.

Keycloak is published under the free Apache 2.0 license.

Keycloak is based on standard protocols and provides support for OpenID Connect, OAuth 2.0, and SAML.