The Connect desktop app uses its configured Registration Host and performs a DNS SRV lookup on _pexapp._tcp. See Registering devices to Pexip Infinity for more information on the Pexip Infinity registrar service, including how to configure device aliases and their associated authentication options. Non-SSO: the username and password credentials associated with the device alias are used to authenticate the registration.įor any given alias, we recommend that you enable Connect app registrations for either SSO or non-SSO authentication, not both.SSO: the Connect app uses Single Sign-On (SSO) services such as AD FS to authenticate the registration.When configuring a device alias, you can specify whether and how a Connect app that is attempting to register with that alias should authenticate itself (authentication is optional but recommended): When registering a Connect app to Pexip Infinity, the alias being registered by the Connect app must match one of the entries on the Management Node under Users & Devices > Device aliases. This topic covers the client authentication options, the DNS requirements, how to provision the clients, some example provisioning email template content, and a description of the associated user experience. The mobile clients do not support provisioning, registration or branding/customization. The Connect desktop app can also be provisioned with branding details, allowing it to use the same branding as used by the web app. You do not need to register your device in order to make calls. use directory services to filter and lookup the contact details (phone book) of other devices or VMRs that are set up on the Pexip Infinity platform, making it easier to call those addresses.The Connect desktop app can register to a Pexip Infinity Conferencing Node. Registering and provisioning the Connect desktop app
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |