Skip to content

Commit

Permalink
fixes of asciidoc markup in many files, minor visual fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
virgo47 committed Oct 20, 2021
1 parent 5436f5a commit 41295da
Show file tree
Hide file tree
Showing 4 changed files with 16 additions and 8 deletions.
11 changes: 8 additions & 3 deletions docs/cases/workflow-3/legacy-pre-3-5-workflow-configuration.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -142,12 +142,17 @@ Default is "true" (i.e. enabled).


| _aspect name_
| Configuration related to this particular aspect - available for standard aspects (listed in the table below).For example, such aspects can be enabled (by simply providing any configuration related to them) or disabled (by explicitly setting their enabled property to false).
| Configuration related to this particular aspect - available for standard aspects (listed in the table below).
For example, such aspects can be enabled (by simply providing any configuration related to them) or disabled (by explicitly setting their enabled property to false).
Note that some aspects are enabled by default - they work even if not mentioned in the configuration.Some aspects can derive approval information (e.g. approverRef, approverExpression, approvalSchema, automaticallyApproved) from objects that they deal with.
For example, add/modify role/resource assignment aspects pull these information from the respective Role, Org, or Resource object.
However, other aspects (like addUserAspect) have no such data available.
These require that this information is provided within the aspect configuration.Note that you can specify approverRef, approverExpression, approvalSchema, or automaticallyApproved attributes even for the aspects that take this information from role, org or resource.
In this case, the information provided within the aspect configuration override the information contained in role/org/resource.*Beware, currently it is not possible to provide _<aspectName>_ configuration with no parameters.* This is due a to a problem in prism parsing.
These require that this information is provided within the aspect configuration.
Note that you can specify approverRef, approverExpression, approvalSchema, or automaticallyApproved attributes even for the aspects that take this information from role, org or resource.
In this case, the information provided within the aspect configuration override the information contained in role/org/resource.

*Beware, currently it is not possible to provide _<aspectName>_ configuration with no parameters.*
This is due a to a problem in prism parsing.
Use at least the following content: <enabled>true</enabled>.


Expand Down
2 changes: 1 addition & 1 deletion docs/concepts/clockwork/scripting-hooks.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ Following scripting hook removes all assignments from disabled users. Please not
UserType user = (UserType) focus;
ActivationStatusType administrativeStatus = user.getActivation().getAdministrativeStatus();
if (administrativeStatus == ActivationStatusType.DISABLED) {  
if (administrativeStatus == ActivationStatusType.DISABLED) {
changed = false;
for (AssignmentType assign : user.getAssignment()) {
assignmentDelta = ContainerDelta.createModificationDelete(UserType.F_ASSIGNMENT, UserType.class, prismContext, assign.clone());
Expand Down
3 changes: 1 addition & 2 deletions docs/deployment/midpoint-home-directory/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -82,11 +82,10 @@ MidPoint will try to create the `midpoint.home` directory if it does not already

|===

== `config.xml` file
== Configuration file

File `config.xml` located in `midpoint.home` directory is the initial midPoint configuration file.


This is not to be confused with
link:/midpoint/reference/concepts/system-configuration-object/[System Configuration Object]
which is already a midPoint object stored repository.
Expand Down
8 changes: 6 additions & 2 deletions docs/security/credentials/password-storage-configuration.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -135,8 +135,12 @@ MidPoint will NOT be able to get a cleartext form of the credential, but it can
| `none`
| MidPoint will not store the credential at all.
MidPoint will only work with credential in the memory while it is needed to complete current operation.
The credential will be discarded after the operation.*This is only partially implemented in midPoint 3.6 and it is not fully supported.*MidPoint should be able not to store the credentials when this setting is used.
But there may be side effects that are not completely addressed yet.This is not entirely tests and not supported.
The credential will be discarded after the operation.

*This is only partially implemented in midPoint 3.6 and it is not fully supported.*
MidPoint should be able not to store the credentials when this setting is used.
But there may be side effects that are not completely addressed yet.
This is not entirely tests and not supported.
Use at your own risk.


Expand Down

0 comments on commit 41295da

Please sign in to comment.