# Updated OpenID Connect breaks using EdDSA algo

**URL:** <https://help.nextcloud.com/t/updated-openid-connect-breaks-using-eddsa-algo/234499>\
**Category:** ℹ️ Support\
**Tags:** github\_issue\_exists, user\_oidc, openidconnect, nc31\
**Created:** [October 22, 2025, 6:22pm UTC](https://help.nextcloud.com/t/updated-openid-connect-breaks-using-eddsa-algo/234499 "2025-10-22T18:22:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![flotillaropes](https://help.nextcloud.com/letter_avatar/flotillaropes/32/5_5575768a8748004e209b776fc1b2916d.png) [@flotillaropes](https://help.nextcloud.com/u/flotillaropes)\
**Post date:** [October 22, 2025, 6:22pm UTC](https://help.nextcloud.com/t/updated-openid-connect-breaks-using-eddsa-algo/234499/1 "2025-10-22T18:22:31Z")

</div>

On nextcloud 31.0.9 and updated OpenID Connect app to 8.1.0. Immediately after update I am unable to login using my Identity provider.

Note, this has always worked before with this EdDSA algo set in my identity provider. The update broke it.

Why would OpenId Connect stop supporting this more secure popular algo?

To reproduce, use EdDSA algo and click the login with your identity provider button. It prompts for my passkey, then displays error page:

Internal Server Error

The server was unable to complete your request.If this happens again, please send the technical details below to the server administrator.More details can be found in the server log.

Log shows:  
Error: Unsupported JWT alg: EdDSA

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [October 22, 2025, 7:02pm UTC](https://help.nextcloud.com/t/updated-openid-connect-breaks-using-eddsa-algo/234499/2 "2025-10-22T19:02:00Z")

</div>

> [@flotillaropes](#):
>
> Note, this has always worked before with this EdDSA algo set in my identity provider. The update broke it.
> 
> Why would OpenId Connect stop supporting this more secure popular algo?

I don’t believe it was intentional. It looks like it may be an oversight related to some algorithm checking code that was just added:

[https://github.com/nextcloud/user\_oidc/pull/1220](https://github.com/nextcloud/user_oidc/pull/1220)

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [January 20, 2026, 7:02pm UTC](https://help.nextcloud.com/t/updated-openid-connect-breaks-using-eddsa-algo/234499/3 "2026-01-20T19:02:32Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.