[
https://issues.apache.org/jira/browse/GUACAMOLE-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712512#comment-17712512
]
Jason Bean edited comment on GUACAMOLE-1773 at 4/14/23 7:42 PM:
----------------------------------------------------------------
Looking at the release notes for jose4j it appears there are some dependencies
for Java 11. I'm not sure it's applicable in my case but one thing I did notice
about the exception is it shows the key being used is RSA256. jose4j 0.6.5 was
updated to support RSASSA-PSS available in Java 11. I don't know if the two
things are related but since, in my case, Java 8 produces an exception in
jose4j while Java 11 doesn't there might be something to it.
[https://bitbucket.org/b_c/jose4j/wiki/Release%20Notes]
was (Author: taddeusz):
Looking at the release notes for jose4j it appears there are some dependencies
for Java 11. I'm not sure it's applicable in my case but one thing I did notice
about the exception is it shows the key being used is RSA256. jose4j 0.6.5 was
updated to support RSASSA-PSS available in Java 11. I don't know if the two
things are related but since, in my case, Java 8 produces an exception in
jose4j while Java 11 doesn't there might be something to it.
[jose4j Release Notes|[https://bitbucket.org/b_c/jose4j/wiki/Release%20Notes]]
> OpenID Login Stopped Working With 1.5.0
> ---------------------------------------
>
> Key: GUACAMOLE-1773
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1773
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-openid, guacamole-docker
> Affects Versions: 1.5.0, 1.5.1
> Reporter: Jason Bean
> Priority: Major
> Attachments: catalina.out
>
>
> Since upgrading from 1.4.0 to 1.5.0 and now 1.5.1 my OpenID configuration
> with Authentik stopped working. If I downgrade to 1.4.0 it starts working
> again. I've attached the output from Tomcat. The exception it gets seems to
> be related to the jwks response but since this works fine from 1.4.0 I can
> only assume there's something wrong with the request being sent from 1.5.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
