Table of Contents

8.2 - Lapis

Main milestones:

Identity extended attributes supports authorization policies per field

Since version 8.2.0, it is possible to define permissions not only for identity as a whole, but also for individual attributes. This means that it is now possible for one user to view (or edit) all his attributes, and for example only one attribute for the other user.

The permissions control for a particular attribute is now available for extended attributes (EAV) only.

More about this feature you can find here.

Single-sign-on (SSO)

Unauthenticated users come to CzechIdM for the first time. Without the need to fill any login or password, they are authenticated to CzechIdM and come to the front page.

More about this feature you can find here.

Bulk action for roles

Bulk actions on roles is used for made easy and asynchronous changes on more roles. This actions are supported now:

Invoke account management action

This operation invokes account management for each selected role. The account management will be invoke for all users with the role. Account management itself and subsequent provisioning are performed asynchronously. You can see progress of this operations in the Events agenda.

Remove roles action

On choosing that action is shows to user counts of relationships on the identities for selected roles.

More about this feature you can find here.

Show additional informations for bulk actions

In some cases, we need obtain additional information and show them to the user before bulk operation starts. For example operation for invoke account management for all identities witch the role. In this case we want to show how many identites has that role (before start).

Prevalidate feature was developed exactly for this case. Every bulk operation has method prevalidate, returns the ModelResults.

More about this feature you can find here.

Module archetype generator

Archetype generate basic skeleton application for our devstack, including backend and frontend module.

With this archetype you can easily generate app skeleton. With this folder structure:

./idm-<your-artefact-id>/
 ├── Realization/                           ⟵ Realization folder (contains FE + BE)
 |   ├── frontend                           ⟵ frontend module
 |   |   └── czechidm-<your-artefact-id>/
 |   |       ├── src                        ⟵ frontend sources
 |   |       ├── test                       ⟵ frontend tests
 |   |       ├── component-descriptor.js
 |   |       ├── module-descriptor.js
 |   |       ├── package.json
 |   |       └── routes.js
 |   └── backend                            ⟵ backend module
 |       └── idm-<your-artefact-id>/
 |           ├── src                        ⟵ backend sources
 |           |   ├── main/
 |           |   └── test/
 |           └── pom.xml                    ⟵ backend pom.xml
 └── pom.xml                                ⟵ artefact pom.xml (you can remove this pom)

More about this feature you can find here.

All solved tasks (without defects) in this version:

All defects fixed in this version: