Quelltext der Seite CSSCurrent en:Microsoft Exchange Online with OAuth2 Authentication

==Introduction==
The Cryptshare Server can send emails via Microsoft Exchange Online. Since Microsoft has discontinued basic authentication for connecting to the SMTP interface, the Cryptshare Server is now able to access this interface via OAuth 2.0 authentication.
==App registration in the Microsoft Entra platform==
{{NoteBox|title=The setup steps are subject to change at any time|content=Microsoft may change the exact application registration process without prior notice. We recommend that you [https://learn.microsoft.com/de-de/entra/identity-platform/quickstart-register-app familiarise yourself with the current process for registering an application with the Microsoft Identity Platform.]}}{{NoteBox|title=Cryptshare for OWA already configured? Separate configuration required!|content=If you are already using Cryptshare for OWA, it is necessary to create a separate configuration due to different permissions and processes.}}
#Log in to the [https://entra.microsoft.com/ Microsoft Entra Admin Centre]. To do this, please use at least one account with the access rights of a [https://learn.microsoft.com/de-de/entra/identity/role-based-access-control/permissions-reference#cloud-application-administrator cloud application administrator].
#If you have access to multiple tenants/directories, ensure that you have selected the tenant you wish to use with the Cryptshare Server by clicking on the settings cog at the top. [[File:EntraSettings.png|border|none]] [[File:CurrentEntraDirectory.png|border|none|500px]]
#Use the sidebar to open 'Identity -> Applications -> App Registrations'[[File:EntraAppRegistrations.png|border|none]]
#Register a new application using the ‘New Registration’ button.[[File:EntraNewRegistration.png|border|none|500px]]
#Create your new application with the following settings:[[File:OAuthEntraRegistering.png|border|none|500px]]
#*The name of the application can be chosen freely.
#*Select the account type ‘Only accounts in this organisational directory (<your company name> only - single tenant)’.
#*Do not set a redirect URI.
#Once the application has been registered, please copy the ‘Application ID (client)’ and the directory ID (tenant).[[File:Application and tenant ids.png|border|none]]
#In the sidebar of the app registration, select the menu item ‘Certificates & Secrets’, then the tab ‘Secret Client Keys’ and then the button ‘New Secret Client Key’.
#* The description can be freely chosen.
#* Select the desired Valid Until value. The maximum duration that can be selected is two years. Please note that after this period has expired, you must create a new secret client key and store it in the Cryptshare Server so that the Cryptshare Server will still be able to send emails after the expiry date. We recommend setting up a calendar entry or other reminder. 
#* Then click on the ‘Add’ button.
#* On the next page, you will see the secret client key that has been created. Copy the string displayed in the “”'Value'“” column (not the Secret ID). The secret client key is only displayed once and cannot be viewed again after leaving the page. [[File:New client secret.png|border|none|[[File:Client secret.png|border|none]]]]
# Next, select the ‘API permissions’ menu item in the sidebar of the app registration.
# Use the ‘Add permission’ button, then select the ‘APIs used by my organisation’ tab and add the “”'SMTP.SendAsApp'“” '“'application permissions”'' in the “”'Office 365 Exchange Online'“” section so that they are displayed in the list. [[File:Add permission.png|border|none|[[File:Office exchange 365.png|border|none]]]][[File:Application permissions.png|border|none]][[File:Smtp sendasapp.png|border|none]]
# Then click “”'Grant admin consent for <your company name>“”' and confirm with “”'Yes'“”.[[File:Grant admin consent.png|border|none]]
# Go to the “”'Company apps'“” section and copy the value from the “”'Object ID'“” column of your newly added application. (Please note: this object ID is different from the object ID found in the App registrations menu item. The object ID from the Enterprise App menu item is required for one of the subsequent steps.)[[File:Object id.png|border|none]]
# Now continue with the configuration in Exchange Online PowerShell.

== App configuration in Exchange Online PowerShell ==
{{NoteBox|title=The setup steps are subject to change at any time|content=Microsoft may change the exact application registration process without prior notice. We recommend that you [https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/ how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth#use-client-credentials-grant-flow-to-authenticate-smtp-imap-and-pop-connections to familiarise yourself with the current process for registering an application with the Microsoft Identity Platform.}}
# Open a PowerShell console on your local Windows PC.
# Install and connect to Exchange Online PowerShell:
## The Exchange Online PowerShell scripts have not been digitally signed by Microsoft. Therefore, it is necessary to allow unsigned scripts to run: <code>Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process</code> .
## Install the ExchangeOnlineManagement modules: <code>Install-Module -Name ExchangeOnlineManagement</code>
## Make the installed modules available in the current PowerShell session: <code>Import-module ExchangeOnlineManagement</code> 
## Connect to Exchange Online using your directory ID (tenant) from step 6 above: <code>Connect-ExchangeOnline -Organisation <Directory ID></code>
## In the window that opens, log in to Microsoft Entra.
# Create a new service principal for the application using the application ID (client) from step 6 and the object ID from step 11: <code>New-ServicePrincipal -AppId <application ID> -ObjectId <object ID></code>
# Then list all existing service principals with <code>Get-ServicePrincipal | fl</code> and find the entry whose AppId (application ID) and ObjectId (object ID) are identical to those used in the previous step. From this entry, you then need the value of the service principal ID specified under “”'Sid'“”.
# Now assign the necessary permissions to the email address that will be used to send Cryptshare emails: <code>Add-MailboxPermission -Identity ‘<sender email address>’ -User <service principal ID> -AccessRights FullAccess</code>.
# Now continue with the configuration on the Cryptshare server.

==Configuration on the Cryptshare server==
[[File:Oauth2 setting.png|mini]]
#Connect to the Cryptshare administration interface.
#Navigate to the System Settings -> Mail Server menu.
#There, select the value ‘“”'Microsoft Exchange Online with OAuth2 authentication'“”’ as the “”'SMTP server type'“”. 
#Ensure that the email address for which the mailbox permission was previously created is entered in the “”'Sender email address'“” field. 
#Ensure that the checkbox next to “”'Allow use of individual sender addresses.“”' is unchecked.
#In the “”'Directory (tenant) ID'“” field, enter the value of the “”'Directory ID (tenant)“”' from step 6. 
#In the “”'Application (client) ID'“” field, enter the value of the “”'Application ID (client)“”' from step 6. 
#In the “”'Client Secret'“” field, enter the value of the “”'Client Secret'“” from step 7. 
#Click “”'Save changes'“”.
#You can send yourself a test email by entering any email address in the “”'Test with email address'“” field and clicking “”'Send test message'“”.
#Then make sure that the same “”'Sender Email Address'“” is also defined in the policy rules and that the “”'Allow use of individual sender addresses'“” checkbox is not selected.