Unable to use the VoidAuth logo url in an OIDC app #452

New issue

Closed

opened 2026-05-30 15:47:49 -05:00 by afloarea · 2 comments

afloarea commented

2026-05-30 15:47:49 -05:00

(Migrated from github.com)

Describe the bug:

I configured Forgejo as an OIDC app in VoidAuth. Forgejo accepts an Icon URL for the authentication source.
This is used on the app authentication page on the 'Sign in with VoidAuth' button.

Trying to set https://voidauth.example.com/logo.svg as the Icon URL does not work. When the forgejo login page is loaded, the request for the voidauth logo fails with NS_ERROR_DOM_CORP_FAILED.

If I understand correctly, this is because the request for the logo receives a response with the header cross-origin-resource-policy: same-origin. Perhaps this header is not necessary or could be set to cross-origin for the logo?

### Describe the bug: I configured Forgejo as an OIDC app in VoidAuth. Forgejo accepts an Icon URL for the authentication source. This is used on the app authentication page on the 'Sign in with VoidAuth' button. Trying to set https://voidauth.example.com/logo.svg as the Icon URL does not work. When the forgejo login page is loaded, the request for the voidauth logo fails with `NS_ERROR_DOM_CORP_FAILED`. If I understand correctly, this is because the request for the logo receives a response with the header `cross-origin-resource-policy: same-origin`. Perhaps this header is not necessary or could be set to `cross-origin` for the logo?

❤️ 1

notquitenothing commented

2026-06-17 19:16:26 -05:00

(Migrated from github.com)

This should now be fixed in a recent release

🎉 1

afloarea commented

2026-06-19 15:44:50 -05:00

(Migrated from github.com)

Indeed, it works after upgrading 🎉️. Thank you for looking into it 🙏️