Narcís Giménez Gelpí <[email protected]> writes: > I am handling a project for a University where the customer is requesting > to have Authentication and Single Sign-on (SSO) over its own OpenLDAP > database via CAM or SAML protocols. > > Linphone will be a softphone connected to a Mitel's PBX but needs to be > compliant with this "opensource" part. So to say, Linphone should be able > to login via SSO (using single and existing user credentials from the > university's IT cloud services) and authenticate against their own OpenLDAP > but still be registered to a standard PBX.
SSO generally refers to having an authentication/authorization provider where only that provider handles user credentials and then services rely on that provider's assertions. It is not generally used to mean "user has a single username/password and uses them with all things". (I had never heard of CAM and don't find much about it in a quick search.) I found this quickly; it may not be the best summary and it may not even be correct: https://www.csoonline.com/article/3232355/what-is-saml-how-it-works-and-how-it-enables-single-sign-on.html So my suggestion is that you should first understand SSO in general and the SSO scheme at this University, including SSO with SIP. Then, you can look at linphone. I am not aware of linphone having SSO capability. You might make a commercial inquiry to Belladone, and the appopriate venue for that is their contact form, not this users' list. (As I try to remember to say to everyone: please do not send me offlist followup questions to my onlist suggestions -- those will be deleted unread.)
signature.asc
Description: PGP signature
_______________________________________________ Linphone-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/linphone-users
