Merge branch 'docs/cleanup-4.8' into support-4.8

docs/diag/logging/log-viewer/index.adoc

@@ -8,7 +8,7 @@
 :page-experimental: true
 :page-tag: guide
 :page-toc: top
-:page-upkeep-status: green
+:page-upkeep-status: red
 
 
 In order to facilitate viewing large log files we have created a tool called midPoint Log Viewer.
@@ -590,8 +590,8 @@ java com.evolveum.logviewer.utils.truncater.Truncater idm.log
 
 == Installation
 
-The log viewer is now part of Eclipse plugin.
-For installation instructions, please see xref:/midpoint/reference/legacy/eclipse-plugin/install/install/[Eclipse plugin installation HOWTO].
+The log viewer is now part of midPoint Studio.
+For installation instructions, please see xref:/midpoint/tools/studio/[midPoint Studio].
 
 Note: when working with any non-trivial log files, increase the heap for Eclipse to at least 2 GB.
 The larger files, the bigger heap is required.

docs/expressions/expressions/script/index.adoc

@@ -23,8 +23,6 @@ Currently supported languages are:
 
 * xref:/midpoint/reference/misc/notifications/velocity/[Velocity] (since 3.4.1) for expressions returning strings/texts
 
-(xref:xpath.adoc[XPath version 2] was supported until midPoint 3.5, but it is not supported any longer)
-
 [NOTE]
 ====
 While you can use any of the languages above, using Groovy is your best bet.

docs/interfaces/invoking-midpoint-services/index.adoc

@@ -162,34 +162,6 @@ There are some information and examples how to use this interface:
 
 * *TODO*: example usage from scripts
 
-== Web Service Interface
-
-Main article: xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface]
-
-xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface] is a SOAP-based web service interface to midPoint.
-It provides operations that are very similar to Java-based xref:/midpoint/reference/interfaces/model-java/[IDM Model Interface], however there are some necessary adjustments.
-The xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface] is strongly RPC-based as this approach is dictated by the technology (SOAP, WSDL).
-Also input-output objects (pass-by-reference) cannot be used and the use of callbacks is beyond practical usability therefore the interface is slightly simplified to overcome these limitations.
-The objects and deltas are expected to be presented as XML objects.
-Full WSDL and XSD definitions are available.
-The interface was developed in a contract-first fashion therefore the WSDL and XSD are authoritative definitions.
-
-There is also a xref:/midpoint/reference/legacy/soap-client/[Model Web Service Client] library based on Java and pure JAX-WS and JAX-B.
-It is designed to be used outside midPoint, e.g. in applications that need to invoke midPoint services.
-
-There are few examples of the interface use:
-
-* xref:/midpoint/reference/legacy/soap-client/sample/[Model Web Service Client Sample] describes a sample code which is part of midPoint source code.
-This sample code is using model client library to invoke midPoint web service.
-
-Note: xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface] is still "version 1" interface.
-While the other interfaces were updated to midPoint version 2 releases this interface remains in roughly the state as it was in midPoint version 1 releases.
-One of the reasons is compatibility.
-Basic midPoint architecture haven't changed much from version 1 to version 2 and therefore we have decided it is not worth to update this interface and that it is better to keep it in the same "XML" spirit of midPoint version 1 (this is SOAP which means it is heavily based on XML anyway).
-There was also very little user demand to update it.
-Currently we have no plans to expand this interface in any significant manner.
-However we will still maintain it and it will remain in this form as part of midPoint for any foreseeable future.
-We do not rule out even the extension and update of this interface in case there is a user demand.
 
 == REST Interface
 
@@ -212,6 +184,4 @@ However informal documentation is (will be) available and there is also a xref:/
 
 * xref:/midpoint/reference/interfaces/model-java/[IDM Model Interface]
 
-* xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface]
-
 * xref:/midpoint/reference/interfaces/rest/[REST API]

docs/interfaces/model-java/index.adoc

@@ -5,7 +5,7 @@
 :page-wiki-metadata-create-date: 2011-09-27T10:53:12.691+02:00
 :page-wiki-metadata-modify-user: semancik
 :page-wiki-metadata-modify-date: 2019-09-08T14:02:14.858+02:00
-:page-upkeep-status: orange
+:page-upkeep-status: red
 :page-upkeep-note: is this s right concept to describe interfaces?
 
 *Version:* 4.4 +
@@ -26,9 +26,6 @@ Implementation of this interface are enforcing a consistency of access control d
 
 For general introduction to interface concepts please see xref:/midpoint/architecture/concepts/common-interface-concepts/[Common Interface Concepts] page.
 
-There is also a web service version of this interface.
-See xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface] for description.
-
 
 == History
 
@@ -129,7 +126,7 @@ Update to adapt to midPoint 3.0 changes.
 
 | 0.1
 | September 2011
-| Initial version derived from xref:/midpoint/reference/legacy/soap/[IDM Model Web Service Interface]
+| Initial version derived from xref:/midpoint/reference/before-4.8/legacy/soap/[IDM Model Web Service Interface]
 | Radovan Semancik
 
 
@@ -269,4 +266,4 @@ development)
 
 == See Also
 
-* xref:/midpoint/reference/interfaces/model-java/introduction/[IDM Model Interface Introduction]
+* xref:/midpoint/reference/interfaces/model-java/introduction/[IDM Model Interface Introduction]

docs/misc/notifications/sending-custom-notifications.adoc

@@ -135,7 +135,6 @@ An example of such bulk action:
 
 More examples can be found in link:https://github.com/Evolveum/midpoint-samples/blob/master/samples/tasks/bulk-actions/send-notifications-about-all-users.xml[samples] and tests (link:https://github.com/Evolveum/midpoint-samples/blob/master/model/model-intest/src/test/resources/scripting/notification-about-jack.xml[here] and link:https://github.com/Evolveum/midpoint-samples/blob/master/model/model-intest/src/test/resources/scripting/notification-about-jack-type2.xml[here]; see also link:https://github.com/Evolveum/midpoint-samples/blob/master/model/model-intest/src/test/resources/common/system-configuration.xml[related system configuration]).
 
-These bulk actions can be also generated by xref:/midpoint/reference/legacy/eclipse-plugin/[the Eclipse plugin], since 0.10.3.
 
 == Using Java code
 

docs/misc/reports/configuration/index.adoc

@@ -3,11 +3,6 @@
 :page-toc: top
 :toclevels: 3
 
-[TIP]
-.MidPoint 4.4 and later
-This feature is available only in midPoint 4.4 and later.
-For configuration before 4.4 please see xref:../configuration-before-4-4/[Report Configuration before midPoint version 4.4].
-
 Native reports are intended to be native reporting mechanism for midPoint.
 The aim is to use what midPoint provides without the need for Jasper framework.
 Jasper framework was removed in midPoint 4.4.

docs/security/advisories/017-self-registration-allows-to-change-password.adoc

@@ -30,4 +30,4 @@ If the self registration is enabled, the attacker can change password of existin
 * Update to latest maintenance midPoint release which contains fix.
 * Reconfigure post registration and post registration link generation to use invitation authentication sequence.
 ** See updated xref:/midpoint/reference/misc/self-registration[Self Registration documentation] for midPoint 4.6.1 and 4.7.1.
-** See xref:/midpoint/reference/misc/self-registration/configuration-before-4-6/[Self Registration configuration before 4.6] for midPoint 4.4.5.
+** See xref:/midpoint/reference/before-4.8/misc/self-registration/configuration-before-4-6/[Self Registration configuration before 4.6] for midPoint 4.4.5.