[
https://issues.apache.org/jira/browse/GUACAMOLE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642093#comment-17642093
]
Tim Worcester edited comment on GUACAMOLE-1668 at 12/1/22 6:14 PM:
-------------------------------------------------------------------
Adding relation to GUACAMOLE-1200 where I wanted to get the Auth code Flow
hooked up. I was able to get around implementing it in the short term by tying
oauth2proxy to my nginx ingress and swapping Guacamole to use auth headers.
was (Author: ghost_knight):
Adding relation to 1200 where I wanted to get the Auth code Flow hooked up. I
was able to get around implementing it in the short term by tying oauth2proxy
to my nginx ingress and swapping Guacamole to use auth headers.
> OpenID implementation of Azure not compatible with Get request
> --------------------------------------------------------------
>
> Key: GUACAMOLE-1668
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1668
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-openid
> Affects Versions: 1.4.0
> Reporter: Hiram Amador
> Priority: Minor
>
> I just noticed in the logs that the token URL is requested using a get method
> in guacamole.
> When trying to use a get with the Microsoft token page, an HTML file is sent
> with an error message saying that the only acceptable methods for the token
> page are POST or OPTION.
> The OpenID implementation might need a way to configure the token request to
> use POST or OPTION to retrieve the token.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
