Chapter 3. Breaking changes

In previous versions of Red Hat Developer Hub, guest authentication was enabled by default. As of Developer Hub 1.2, guest authentication is disabled by default and needs to be explicitly enabled for use.

The guest login is provided by a special authentication provider that must be explicitly enabled. This authentication provider should be used for development purposes only and is not intended for production, as it creates a default user that has user-level access to the Developer Hub instance.

In this release, Developer Hub provides more strict validation on the source of permission policies and roles based on how you define the first role.

This update improves the validation of the different sources of permission policies and roles and provides more consistent policy definition. If a permission policy or role with a new member does not match the originating role’s source, Developer Hub prevents any update to permissions. Sources include 'REST, 'CSV', 'Configuration', and 'legacy'.

Before updating your Red Hat Developer Hub application, you should migrate all permission policies and roles to a single source based on their respective roles. This can be done by using the GET roles endpoint to review the source information and by querying the role-metadata table of the permission database. You can make updates to permission policies by using one of the following: REST API, CSV file, and the database.