We are proud to announce the availability of Add-On Self Administration 1.8 and Add-On Administration 1.8. This release mostly brings compatibility fixes to make the add-ons work with all versions of OSIAM >= 2.2 again. Support for OSIAM 3.0 has been added too. A major bug in Add-On Administration was fixed as well.

You can download the add-ons in different packaging formats using one of the following links:

It follows an overview of the most important changes. See the full changelogs at the Add-On Self Administration 1.8 release page on GitHub and the Add-On Administration 1.8 release page on GitHub.

Add-On Self Administration

Compatibility

In release 1.7 the Add-On Self Administration introduced an incompatibility with versions of OSIAM <= 2.3. This release restore this compatibility. To connect to OSIAM <= 2.3, you have to set the configuration property org.osiam.connector.legacy-schemas to true:

org.osiam.connector.legacy-schemas=true

For more information see the Add-On Self Administration documentation.

Also, support for OSIAM 3.0 has been added. To connect to OSIAM 3.0, you have to use the configuration property org.osiam.home instead of the other endpoint properties:

org.osiam.home=http://localhost:8080/osiam

For more information see the Add-On Self Administration documentation.

Changed Scopes

The Add-On Self Administration now uses the scope ADMIN to connect to OSIAM. With this we are dropping support for the deprecated method-based scopes. This means you have to update the respective OAuth client before you can update the add-on. To do this issue the following SQL statement:

INSERT INTO osiam_client_scopes (id, scope) VALUES (<id of addon-self-administration-client>, 'ADMIN');

Most of the time <id of addon-self-administration-client> will be 10. If you have a non-standard setup, then it might have a different value.

Plug-In API 1.5

A new version of the Add-On Self Administration Plug-In API has been released. It’s built against the latest SCIM schema and we changed the dependency on it to scope provided. See the full changelog and downloads at the Add-On Self Administration Plug-In API 1.5 release page on GitHub.

Add-On Administration

Compatibility

In release 1.7 the Add-On Administration introduced an incompatibility with versions of OSIAM <= 2.3. This release restore this compatibility. To connect to OSIAM <= 2.3, you have to set the configuration property org.osiam.connector.legacy-schemas to true:

org.osiam.connector.legacy-schemas=true

For more information see the Add-On Administration documentation.

Also, support for OSIAM 3.0 has been added. To connect to OSIAM 3.0, you have to use the configuration property org.osiam.endpoint instead of the other endpoint properties:

org.osiam.endpoint=http://localhost:8080/osiam

For more information see the Add-On Administration documentation.

Changed Scopes

The Add-On Administration now uses the scope ADMIN to connect to OSIAM. With this we are dropping support for the deprecated method-based scopes. This means you have to update the respective OAuth client before you can update the add-on. To do this issue the following SQL statement:

INSERT INTO osiam_client_scopes (id, scope) VALUES (<id of addon-administration-client>, 'ADMIN');

Most of the time <id of addon-administration-client> will be 20. If you have a non-standard setup, then it might have a different value.

Boolean Types Extension Fields

Due to a bug, all boolean-types extension fields always displayed the value as true, regardless of the real value stored. Furthermore it was not possible to set the fields to anything else than true. This release fixes this behavior so you can safely use boolean-typed extension fields again. See also: https://github.com/osiam/addon-administration/issues/83.