CSSCurrent en:Cryptshare for OWA: Unterschied zwischen den Versionen

Aus Cryptshare Documentation
Wechseln zu:Navigation, Suche
(Imported from text file)
 
K
 
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 23: Zeile 23:


=== Scenario 1 - Transfer from a different Cryptshare Server ===
=== Scenario 1 - Transfer from a different Cryptshare Server ===
In the following example, User A sends a Cryptshare Transfer to User B, using their own Cryptshare Server, "Cryptshare Server A".
In the following example, User A sends a Cryptshare Transfer to User B, using their own Cryptshare Server, "Cryptshare Server A".
[[File:65669656.png]]
[[File:65670371.png|1332x1332px]]
In order for User B to be able to download the Transfer via Cryptshare for OWA, Cryptshare Server B's URL ('https://cryptshare.example.com') has to be allowed in the CORS configuration of Cryptshare Server A.
In order for User B to be able to download the Transfer via Cryptshare for OWA, Cryptshare Server B's URL ('https://cryptshare.example.com') has to be allowed in the CORS configuration of Cryptshare Server A.
[[File:65669687.png]]
 
[[Datei:19 Cryptshare for OWA EN.png]]
=== Scenario 2 - Transfer from the Same Cryptshare Server ===
=== Scenario 2 - Transfer from the Same Cryptshare Server ===
When sending Transfers between Users on the same Cryptshare Server, the CORS configuration will '''not''' be need to be changed.
When sending Transfers between Users on the same Cryptshare Server, the CORS configuration will '''not''' be need to be changed.
[[File:65669655.png]]
[[File:65670370.png]]


-----
-----

Aktuelle Version vom 14. Oktober 2021, 10:00 Uhr



Cryptshare for OWA is an add-on product for Office 365. It can be used in the browser.

General

The administration section for OWA on the Cryptshare Server allows to setup and administer your Cryptshare for OWA clients from the Cryptshare Server administration interface. It is possible to upload new add-on versions in this section in order to provide an Office 365 add-in manifest URL which is required to setup the OWA add-in in the Outlook environment.

Hosted Content
Please note, that the Cryptshare Server is hosting the uploaded content under a dedicated file system location on the server. This is a prerequisite for OWA clients to work properly. Do not manually change content in this directory or add additional resources to it. Cryptshare AG is not responsible for hosting resources other than for the intended purpose and will not grant support services in case of problems caused by not following this requirement.


CORS

CORS (Cross-Origin Resource Sharing) is a system restricting which other web pages can make HTTP requests to a web site or web API. The web-browser only allows a web site to perform HTTP requests against either the origin it is running on (e.g. a site under 'https://cryptshare.example.com/resources/client.owa/index.html' can make requests against other resources on 'https://cryptshare.example.com'), or different origins which explicitly allow the requesting origin to do so. This prevents an attacker, which has tricked a user into visiting a malicious site, from sending unauthorized requests to a legitimate site with the users credentials. This affects Cryptshare for OWA clients when attempting to download Cryptshare Transfers from a Cryptshare Server different from the one the current add-in is installed on. In order to allow the recipients, that users of your Cryptshare Server send Cryptshare Transfers to, to download the transfers in Cryptshare for OWA, you will have to allow their Cryptshare Servers URL in your Cryptshare Servers CORS settings.

Options

The following options are available:

  • Disable: No Cryptshare for OWA instances on other Cryptshare Servers may access this Cryptshare Servers transfers.
  • Individual Hosts: Only the Cryptshare for OWA instances on other Cryptshare Servers for which the other Cryptshare Servers origin has been entered may access this Cryptshare Servers transfers.
  • Allow all: Cryptshare for OWA instances on any Cryptshare Servers may access this Cryptshare Servers transfers.
'Allow all' allows any client to send Cross-Origin Requests to this Cryptshare Server which is a security risk. Intentionally disabling the CORS restriction is not recommended.


Scenario 1 - Transfer from a different Cryptshare Server

In the following example, User A sends a Cryptshare Transfer to User B, using their own Cryptshare Server, "Cryptshare Server A". 65670371.png In order for User B to be able to download the Transfer via Cryptshare for OWA, Cryptshare Server B's URL ('https://cryptshare.example.com') has to be allowed in the CORS configuration of Cryptshare Server A.

19 Cryptshare for OWA EN.png

Scenario 2 - Transfer from the Same Cryptshare Server

When sending Transfers between Users on the same Cryptshare Server, the CORS configuration will not be need to be changed. 65670370.png