Differences

This shows you the differences between two versions of the page.

--- 712:cms_sharepoint_online [2025/09/16 12:51] – Policnik, Florian
+++ 712:cms_sharepoint_online [2025/12/15 15:25] (current) – Policnik, Florian
@@ Line 48: / Line 48: @@
   * Links: [[https://portal.azure.com|Microsoft Azure Portal]]
-> client.secret ** * **
+> client.secret ** * ** //(required if no keystore file is provided)//
   * Description: The client secret, which can be generated after registering the stages application at the Microsoft azure portal website.
   * Links: [[https://portal.azure.com|Microsoft Azure Portal]]
+> client.certificate.keystore.file //(since Stages 7.12.3.0, required if no client secret is provided)//
+  * Description: Path to the keystore file with private key and certificate to authenticate with Azure. Path can be absolute or relative to Stages installation directory.
+> client.certificate.keystore.password //(since Stages 7.12.3.0, required if no client secret is provided)//
+  * Description: Password for the specified keystore file.
+> client.certificate.key.alias //(since Stages 7.12.3.0, required if no client secret is provided)//
+  * Description: Alias of the private key / certificate entry in keystore file.
+> client.certificate.key.password //(since Stages 7.12.3.0, required if no client secret is provided)//
+  * Description: Password of the private key / certificate entry in keystore file.
 > tenant.id ** * **
@@ Line 78: / Line 94: @@
   * Default Value: Document
   * Description: Name of the **document**  content type. Sharepoint supports multiple content types but stages only supports the default type for documents.
-  * Since Stages 7.5.6.2, 7.6.2.4 and 7.7.0.0 it is possible to define multiple content types. Separate them with a #. For example:
+  * It is possible to define multiple content types. Separate them with a #. For example:
 <code xml>
@@ Line 89: / Line 105: @@
   * Description: The second content type which is supported by stages.
   * Known Issue: Typo in Default Value. Has to be Link to a **D**ocument
-  * Since Stages 7.5.6.2, 7.6.2.4 and 7.7.0.0 it is possible to define multiple link types. Separate them with a #. For example:
+  * It is possible to define multiple link types. Separate them with a #. For example:
 <code xml>
@@ Line 104: / Line 120: @@
   * Default Value: download
-  * Description: When set to ''link'', the user will be by linked directly to SharePoint Online. The download option can be chosen from the sub-menu.
+  * Description: When set to ''link'', the user will be linked directly to SharePoint Online. The download option can be chosen from the sub-menu.
-> sites.selected.scope (since Stages 7.10.7.0)
+> sites.selected.scope
   * Default Value: false
@@ Line 112: / Line 128: @@
-==== Proxy configuration (since Stages 7.10.10.0) ====
+==== Proxy configuration ====
 Stages can communicate with SharePoint Online through a proxy. Fill in the ''proxy.scheme'', ''proxy.hostname'' and ''proxy.port'' host properties to use a proxy. Otherwise no proxy is used.
@@ Line 203: / Line 219: @@
 {{ :cms:azure_permissions.png?direct }}
-=== Recommended option: Application and delegated permission Sites.Selected (Since Stages 7.10.7.0) ===
+=== Recommended option: Application and delegated permission Sites.Selected ===
 To active this option the setting ''sites.selected.scope'' has to be set to ''true'' in the xml host properties:
@@ Line 274: / Line 290: @@
 ==== Certificates & secrets ====
-It is required to generate a client secret for Stages. It's recommended to choose expire never or a long duration. If the secret expires it must be changed in Stages and all users have to re-authenticate.
+It is required to generate a client secret or certificate for Stages.
+=== Client Secret ===
+It's recommended to choose expire never or a long duration. If the secret expires it must be changed in Stages.
 [[https://doc.stagesasaservice.com/lib/exe/detail.php?id=74:cms_sharepoint_online&media=cms:azure_certificates_secrets.png|{{:cms:azure_certificates_secrets.png}}]]
+Client secret can be specified like this:
+<code xml>
+<cms-property name="client.secret" value="xxxxxx" />
+</code>
+=== Certificates (Since 7.12.3.0) ===
+It is possible to use certificates instead of client secret. A [[https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-self-signed-certificate|certificate has to be generated]] and added to Azure configuration. A keystore file with private key and certificate has to be configured in Stages:
+<code xml>
+<cms-property name="client.certificate.keystore.file" value="conf/sharepointonline.pfx" />
+<cms-property name="client.certificate.keystore.password" value="keystorepassword" />
+<cms-property name="client.certificate.key.alias" value="myalias" />
+<cms-property name="client.certificate.key.password" value="keypassword" />
+</code>
 ===== Repository Configuration =====