[ 
https://issues.apache.org/jira/browse/GUACAMOLE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356027#comment-16356027
 ] 

Michael Jumper commented on GUACAMOLE-29:
-----------------------------------------

I'm not sure. To me, it seems a bit too much of a corner case to dedicate a 
top-level configuration parameter like the description suggests. I wouldn't be 
against supporting this via an extension, though. Now that the HTTP status code 
is determined completely by {{GuacamoleException}} (due to your changes via 
GUACAMOLE-499), this can actually work. The extension can use its own subclass 
of {{GuacamoleUnauthorizedException}} to specify an HTTP status code of 401.

> Add support for requesting HTTP Basic Authentication
> ----------------------------------------------------
>
>                 Key: GUACAMOLE-29
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-29
>             Project: Guacamole
>          Issue Type: Improvement
>            Reporter: Michael Jumper
>            Priority: Minor
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from 
> [GUAC-1489|https://glyptodon.org/jira/browse/GUAC-1489], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> Some reverse proxies support SSO via HTTP Basic authentication if the server 
> requests it with 401 Unauthorized response.
> As Guacamole already reads Authorization header, it looks trivial to add 
> guacamole.properties option such as "enable-http-basic-auth", to tell 
> Guacamole to request HTTP Basic Authentication .
> PR on its way :)
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to