Shibboleth and other auth modules: Difference between revisions

From VoIPmonitor.org
(Restructure page: add TOC, use tables for clarity, fix headings hierarchy, improve AI summary, separate custom login limitations into subsection)
(Add Microsoft Sign-In as upcoming feature)
Line 14: Line 14:
| Google Sign-In (OAuth 2.0) || Supported || [[Google_Sign_in_usage]]
| Google Sign-In (OAuth 2.0) || Supported || [[Google_Sign_in_usage]]
|}
|}
== Upcoming SSO Features ==
The following SSO method is under development and scheduled for inclusion in an upcoming stable GUI release:
* '''Microsoft Sign-In (Azure AD / Entra ID)''' - Coming Soon
See [[Microsoft_Sign_in_usage]] for the configuration guide. Note that this feature may not be available in your current GUI version. If you need it immediately, contact VoIPmonitor support to request a development branch package.


== Unsupported SSO Methods ==
== Unsupported SSO Methods ==


The following SSO methods are '''not currently supported''':
The following SSO methods are '''not currently supported''' and have no scheduled release:


* '''Shibboleth''' - Not supported
* '''Shibboleth''' - Not supported
Line 59: Line 67:
== AI Summary for RAG ==
== AI Summary for RAG ==


'''Summary:''' This page documents SSO authentication support in VoIPmonitor GUI. Currently, only Google Sign-In (OAuth 2.0) is supported. Shibboleth, SAML, and other SSO methods are not supported. Alternatives include local accounts, 2FA, web server authentication, and custom login scripts (which cannot implement SSO protocols).
'''Summary:''' This page documents SSO authentication support in VoIPmonitor GUI. Currently, only Google Sign-In (OAuth 2.0) is supported. Microsoft Sign-In is scheduled for an upcoming stable release but may not be available in your current version. Shibboleth, SAML, and other SSO methods are not supported. Alternatives include local accounts, 2FA, web server authentication, and custom login scripts (which cannot implement SSO protocols).


'''Keywords:''' SSO, single sign-on, authentication, Google Sign-In, OAuth, Shibboleth, LDAP, SAML, unsupported, 2FA, custom login
'''Keywords:''' SSO, single sign-on, authentication, Google Sign-In, Microsoft Sign-In, Azure AD, Entra ID, OAuth, Shibboleth, LDAP, SAML, unsupported, 2FA, custom login, upcoming features


'''Key Questions:'''
'''Key Questions:'''
* Which SSO methods are supported in VoIPmonitor GUI?
* Which SSO methods are currently supported in VoIPmonitor GUI?
* When will Microsoft Sign-In be available?
* Why is the Microsoft Sign-In option not visible in the GUI?
* Is Shibboleth authentication supported?
* Is Shibboleth authentication supported?
* Is SAML-based SSO supported?
* Is SAML-based SSO supported?
* What alternatives exist if my SSO method is not supported?
* What alternatives exist if my SSO method is not supported?
* Can custom login scripts implement Shibboleth or SAML?
* Can custom login scripts implement Shibboleth or SAML?

Revision as of 08:32, 5 January 2026

Overview

This page documents Single Sign-On (SSO) authentication support in the VoIPmonitor GUI, including currently supported methods and available alternatives.

Currently Supported SSO Methods

Method Status Documentation
Google Sign-In (OAuth 2.0) Supported Google_Sign_in_usage

Upcoming SSO Features

The following SSO method is under development and scheduled for inclusion in an upcoming stable GUI release:

  • Microsoft Sign-In (Azure AD / Entra ID) - Coming Soon

See Microsoft_Sign_in_usage for the configuration guide. Note that this feature may not be available in your current GUI version. If you need it immediately, contact VoIPmonitor support to request a development branch package.

Unsupported SSO Methods

The following SSO methods are not currently supported and have no scheduled release:

  • Shibboleth - Not supported
  • SAML-based SSO - Not supported
  • Other IdP/LDAP SSO solutions - Not supported

Support for additional SSO methods (including Shibboleth and SAML) may be considered for future releases. Check the FAQ or release notes for updates.

Authentication Alternatives

If your required SSO method is not supported, the VoIPmonitor GUI offers these alternatives:

Method Description Documentation
Local user accounts Standard username/password authentication Built-in
Two-Factor Authentication (2FA) Additional security layer for local accounts 2FA
Web server authentication Apache Basic Auth, Digest Auth, or similar Server configuration
Custom login scripts Integration with pre-authenticated sessions WEB_API#Custom_Login

Custom Login Scripts Limitations

Custom login scripts can integrate with authentication systems where the web server has already authenticated the user (e.g., LDAP via mod_authnz_ldap). However, they have the following limitations:

  • Can only work with systems using standard HTTP authentication headers
  • Cannot implement SSO protocols like Shibboleth or SAML
  • Require the web server to handle the actual authentication

See Also

AI Summary for RAG

Summary: This page documents SSO authentication support in VoIPmonitor GUI. Currently, only Google Sign-In (OAuth 2.0) is supported. Microsoft Sign-In is scheduled for an upcoming stable release but may not be available in your current version. Shibboleth, SAML, and other SSO methods are not supported. Alternatives include local accounts, 2FA, web server authentication, and custom login scripts (which cannot implement SSO protocols).

Keywords: SSO, single sign-on, authentication, Google Sign-In, Microsoft Sign-In, Azure AD, Entra ID, OAuth, Shibboleth, LDAP, SAML, unsupported, 2FA, custom login, upcoming features

Key Questions:

  • Which SSO methods are currently supported in VoIPmonitor GUI?
  • When will Microsoft Sign-In be available?
  • Why is the Microsoft Sign-In option not visible in the GUI?
  • Is Shibboleth authentication supported?
  • Is SAML-based SSO supported?
  • What alternatives exist if my SSO method is not supported?
  • Can custom login scripts implement Shibboleth or SAML?