Therefore, EMS applications must be added to a whitelist within the Skype for Business implementation. Unified Communications Web API (UCWA) uses xframe and cross-domain scripting to accomplish the user authentication to leverage the integration. Oauth (Online) – This is the only authentication option for Skype for Business Online Integration.įrom the Everyday User Applications parameters tab, select the Platform Services API URL parameter and click Edit to specify the Platform Services URL.Īdd EMS Applications to the Allowed Domains List. You can choose from the following authentication methods:ĪDFS – The EMS Mobile App does not support ADFS authentication. This determines the authentication type used to generate a token. The client machine and the Web server should have access to the Autodiscover URL.Ĭhoose a Skype for Business Server Authentication Method. Multiple URLs must be separated by commas and cannot contain any spaces. This performs autodiscovery to find the appropriate server to communicate with. This determines the name of the AAD tenant.Įnter the Skype for Business AutoDiscover URL.
This determines the ID of the registered application. In Azure Active Directory Client ID, enter a Client Name. To configure Skype for Business in the EMS Platform Services Admin Portal: Follow the instructions in Prerequisites for Skype for Business Online Integration and Integrate with Skype for Business Online for configuration.ĮMS Software uses Unified Communications Web API 2.0 to integrate with Skype for Business Server and Skype for Business Online. Hybrid – This deployment has the same authentication method as the Online deployment.
Skype for Business Online – This deployment retains the token so only an initial authentication is required. Follow the instructions in Prerequisites for Skype for Business Online Integration and Integrate with Skype for Business Online for configuration.
As a result, you will be asked to sign in every 8 hours. Please follow the instructions in Prerequisites for Skype for Business Server 2015 (On-premise) Integration and Integrate Skype for Business Server for configuration. Skype for Business Server 2015 On Premise – This deployment for Skype for Business does not retain a token and requires authentication every 8 hours. There are three deployment types for Skype for Business: This URI must be verifiable and accessible externally.Įnsure all EMS components have been deployed: Provide EMS Conferencing URI (e.g., app directory/ConferencingLogin.aspx). The following prerequisites are required for the Skype for Business online integration:Įnsure Microsoft Azure Active Directory is installed and functional.Įnsure you have admin access to Azure environment. If you experience certificate errors, please refer to the first step above.Įnsure all EMS components have been deployed: AutoDiscover URL should return an xml file. Multiple URLs must be separated by commas and contain no spaces.Įnsure you can access the URL without certificate errors (EMS Software recommends using the Google Chrome browser). Optionally, you can provide one or more URLs. If a URL is not provided, EMS will build a URL based on the Everyday User's email address. To provide a URL, navigate to the Platform Services Admin Page Conferencing tab. SHA2 is required as major browsers no longer support SHA1. The following prerequisites are required for the Skype for Business Server 2015 (on-premise) integration:Įnsure a SHA2 and above Algorithm certificate is installed and functional. Skype for Business Server 2015 (On-premise) Integration
0 kommentar(er)
