Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:modules_extras [2018/10/22 12:19] sourek created |
devel:documentation:modules_extras [2019/10/24 08:28] kopro information about utils |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== CzechIdM - extras ====== | ||
+ | CzechIdM - extras contains various features, which are not suited to be in any other module. List of the currently supported features is bellow. | ||
+ | Currently supported CzechIdM version : 9.2.2 | ||
+ | |||
+ | ===== Developing and releasing ===== | ||
+ | <note important> | ||
+ | |||
+ | * When developing, use our standard gitflow: | ||
+ | * Branch per feature. Branch naming as usual. | ||
+ | * Develop on top of the '' | ||
+ | * Master branch contains tagged releases. | ||
+ | * The **only** way for code to get into master is by pull request '' | ||
+ | |||
+ | * Release process | ||
+ | - After merging all features wanted for the release, one (selected) developer builds the develop. If it builds fine and tests are also OK, the developer edits module version in '' | ||
+ | - Developer creates pull request on GitHub to merge '' | ||
+ | - Repo admin (or any other authorized user) reviews the pull request, can request changes if necessary. Unresolved TODOs, missing comments, bad codestyle or documentation, | ||
+ | - If the pull request is OK, repo admin merges it. | ||
+ | - Repo admin creates a new release in GitHub interface, version is set to '' | ||
+ | - Repo admin pushes release into BCV Nexus. | ||
+ | - After release, repo admin makes changes on the '' | ||
+ | |||
+ | ===== Virtual system import LRT ===== | ||
+ | Documentation is available here: [[tutorial: | ||
+ | |||
+ | ===== Automatic role definitions - Import of data from CSV LRT ===== | ||
+ | Documentation is available here: [[tutorial: | ||
+ | |||
+ | ===== Assign roles to contract EAV - Import of data from CSV LRT ===== | ||
+ | Documentation is available here: [[tutorial: | ||
+ | |||
+ | ===== Roles - Import of data from CSV LRT ===== | ||
+ | Documentation is available here: [[tutorial: | ||
+ | |||
+ | ===== Automatic roles - adding role by node in structure ===== | ||
+ | Documentation is available here: [[tutorial: | ||
+ | |||
+ | ===== Status task ===== | ||
+ | Documentation is available here: [[tutorial: | ||
+ | |||
+ | ===== SSO authenticate ===== | ||
+ | Documentation is available here: [[documentation: | ||
+ | |||
+ | ===== Guarantees of roles can assign their roles to everybody ===== | ||
+ | This feature enable that if you are guarantee at least for one role then you will see all users and you can assign/ | ||
+ | You can see all user's roles but you can't change the others for which you are not guarantee | ||
+ | |||
+ | For correct behavior you need to configure three new evaluators to userRole: | ||
+ | * IdentityAccessForRoleGuaranteeEvaluator | ||
+ | * IdentityRoleAccessForRoleGuaranteeEvaluator | ||
+ | * RoleRequestAccessForRoleGuaranteeEvaluator | ||
+ | |||
+ | Other thing you need to do is to enable service ExtrasIdmConceptRoleRequestService. This service is by default turned off in extras module. | ||
+ | Go to your project modul and create new service which will inherit from ExtrasIdmConceptRoleRequestService and add annotation Primary and Service. | ||
+ | |||
+ | Update IdmConceptRoleRequestDto is allowed everybody that will change only audited fields or systemState field (this is for update state of whole request after retry mechanism or approving virtual request). | ||
+ | |||
+ | ===== Report Compare values in IdM with values in system ===== | ||
+ | Report will compare value of attributes with connected system. Connected system does not need to be in read only. | ||
+ | More information is available here: [[tutorial: | ||
+ | |||
+ | ===== Notification about the end of identity' | ||
+ | A notification about the end of identity' | ||
+ | More information is available here: [[tutorial: | ||
+ | |||
+ | ===== Get titles before and after ===== | ||
+ | Almost every project receive all titles in one string and IdM allow separates titles before and after. For this case was created in *ExtrasUtils* two methods *getTitlesAfter* and *getTitlesBefore*. And transformation scripts *extrasGetTitlesBefore* and *extrasGetTitlesAfter*, | ||
+ | |||
+ | Dictionary with titles can be setup by configuration properties. Default values exists. | ||
+ | < | ||
+ | idm.sec.bee.configuration.titlesAfter=" | ||
+ | idm.sec.bee.configuration.titlesBefore=" | ||
+ | </ |