Nick Couchman commented on GUACAMOLE-29:

And one more question, here.  Is the idea here that Guacamole throws a 401 
allowing an upstream server to authenticate, and then Guacamole accepts the 
authentication (similar to the Header authentication module)?  Or is the idea 
that Guacamole throws a 401 to trigger authentication, and that the 
authentication information provided gets passed back to Guacamole (perhaps to 
another underlying module) for validation?

> 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

Reply via email to