-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom background image and logo does not work when using external login providers #17441
Comments
Hi there @lrirlu! Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better. We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
Hi @lrirlu , thank you for reporting this issue. |
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
14.3.1
Bug summary
When an external login provider is implemented, it is not possible to configure a custom background image for the login page, cf. this document.
Once the login provider is removed, the configured background appears.
Specifics
No response
Steps to reproduce
Expected result / actual result
Expected
The custom background image shows on the login screen and it is also possible to login using the external login provider.
Actual
The default background image is shown and it is also possible to login with the external login provider.
Additionally
Removing the external login provider, e.g. by deleting the plugin from
App_Plugins
results in the background appearing as expected.The text was updated successfully, but these errors were encountered: