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)
(Redirect to REMOTE_USER_Authentication - page restructured for clarity (Shibboleth is just one of many Apache modules that set REMOTE_USER))
Tag: New redirect
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:SSO Authentication Support}}
#REDIRECT [[REMOTE_USER_Authentication]]
__TOC__
 
== 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 ==
 
{| class="wikitable"
|-
! Method !! Status !! Documentation
|-
| Google Sign-In (OAuth 2.0) || Supported || [[Google_Sign_in_usage]]
|}
 
== Unsupported SSO Methods ==
 
The following SSO methods are '''not currently supported''':
 
* '''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:
 
{| class="wikitable"
|-
! 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 <code>mod_authnz_ldap</code>). 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 ==
 
* [[Google_Sign_in_usage]] - Google OAuth 2.0 setup guide
* [[2FA]] - Two-Factor Authentication configuration
* [[WEB_API#Custom_Login]] - Custom login script documentation
* [[FAQ]] - Frequently Asked Questions
 
== 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).
 
'''Keywords:''' SSO, single sign-on, authentication, Google Sign-In, OAuth, Shibboleth, LDAP, SAML, unsupported, 2FA, custom login
 
'''Key Questions:'''
* Which SSO methods are supported in VoIPmonitor 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?

Latest revision as of 12:42, 6 January 2026