[2/2] syncope git commit: [SYNCOPE-1145] Docs

[il...@apache.org]

[SYNCOPE-1145] Docs


Project: http://git-wip-us.apache.org/repos/asf/syncope/repo
Commit: http://git-wip-us.apache.org/repos/asf/syncope/commit/7047e367
Tree: http://git-wip-us.apache.org/repos/asf/syncope/tree/7047e367
Diff: http://git-wip-us.apache.org/repos/asf/syncope/diff/7047e367

Branch: refs/heads/master
Commit: 7047e367bbc7a4dd4f65bb3e5b23130541c3134d
Parents: 497d2da
Author: Francesco Chicchiriccò <il...@apache.org>
Authored: Fri Jul 7 12:52:22 2017 +0200
Committer: Francesco Chicchiriccò <il...@apache.org>
Committed: Fri Jul 7 12:52:31 2017 +0200

----------------------------------------------------------------------
 .../reference-guide/concepts/externalresources.adoc  | 15 +++++++++++++++
 .../configurationparameters.adoc                     |  6 +++++-
 2 files changed, 20 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/syncope/blob/7047e367/src/main/asciidoc/reference-guide/concepts/externalresources.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc b/src/main/asciidoc/reference-guide/concepts/externalresources.adoc
index d121842..81bbf7f 100644
--- a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc
+++ b/src/main/asciidoc/reference-guide/concepts/externalresources.adoc
@@ -190,3 +190,18 @@ example, which leverage the `syncope:fullPath2Dn()` custom JEXL function:
 * Users: `'uid=' + name + syncope:fullPath2Dn(realm, 'ou', ',') + ',o=isp'`
 * Groups: `'cn=' + name + syncope:fullPath2Dn(realm, 'ou', ',') + ',o=isp'`
 ====
+
+[[connectors-resources-history]]
+[NOTE]
+.Connector Instances and External Resources Configuration History Management
+====
+When either developing an IdM solution or managing a production deployment, it often happens to play with
+Connector Instances and / or External Resources configuration; sometimes, this results in failures which prevent
+<<provisioning,provisioning>> to work properly.
+
+In such situations it is possible to revert a Connector Instance's and / or External Resource's configuration to a
+previous working state.
+
+The maximum number of configurations to keep, for each Connector Instance and for each External Resource, is set by
+`connector.conf.history.size` and `resource.conf.history.size`: see <<configuration-parameters, below>> for details.
+====

http://git-wip-us.apache.org/repos/asf/syncope/blob/7047e367/src/main/asciidoc/reference-guide/workingwithapachesyncope/systemadministration/configurationparameters.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/reference-guide/workingwithapachesyncope/systemadministration/configurationparameters.adoc b/src/main/asciidoc/reference-guide/workingwithapachesyncope/systemadministration/configurationparameters.adoc
index d8246f1..71867f3 100644
--- a/src/main/asciidoc/reference-guide/workingwithapachesyncope/systemadministration/configurationparameters.adoc
+++ b/src/main/asciidoc/reference-guide/workingwithapachesyncope/systemadministration/configurationparameters.adoc
@@ -52,6 +52,10 @@ Suspended Users are anyway not allowed to authenticate.
 * `tasks.interruptMaxRetries` - how many attempts shall be made when interrupting a running <<task,task>>;
 * `return.password.value` - whether the hashed password value shall be returned when reading users;
 * `identity.recertification.day.interval` - number of days between
-<<identity-recertification,identity recertifications>>.
+<<identity-recertification,identity recertifications>>;
+* `connector.conf.history.size` - how many previous configurations shall be kept for each Connector Instance,
+for usage with <<connectors-resources-history, connectors and resources configuration history management>>;
+* `resource.conf.history.size` - how many previous configurations shall be kept for each External Resource,
+for usage with <<connectors-resources-history, connectors and resources configuration history management>>.
 
 Besides this default set, new configuration parameters can be defined to support <<customization,custom>> code.