Organization branding control
With Auth0, my Applications have a Logo URL (which would be handled in Organizations it seems with Kinde). The URL worked well because when my tenant in my multi-tenant platform decided to update their logo, the new logo was available on the sign in page since that logo simply referenced our URL for the logo.
With Kinde it seems that logo needs to be actually uploaded. Ok, little different and definitely more work, but that's ok. The problem comes up when I don't see an API to do so so it actually takes manual intervention to make this happen.
My tenants will not have access to Kinde, they're not going to upload their logo twice, this has to be automated somehow.
Any suggestions?
An alternative would be to allow URL parameters to be passed to the login page to customize the experience and override whatever settings exist for the Organization's brand and the overall brand.
6 Replies
Hey @ryno1234.,
You are totally right, you can do pretty much everything in the Kinde Admin dashboard via our Kinde Management API, except for uploading logos. This is because we haven't landing on the best mechanism for uploading logos via our API.
I will speak to my team about this.
It will be helpful to know more about your business when I go back to my team? Do you have a website I could look at to understand more about your business?
@Oli - Kinde, first off, thanks for the response! A concrete example is https://bestof.wilmingtonncmagazine.com/. You can see from my screenshot we pass some information to make sure the login page is customized.
Vote for the Best
Cast your vote for the finest in town!
To be clear, this is a pretty big deal for us - we cannot monitor when our clients update their logos. Even if we did, we'd have to be reactionary about updating the logos in the Organization just to keep up with whatever change they made. Equally the same thing could happen with the name of their site (they can change the title). That, however, can be handled via your API and is not as important as the logo.
Hey @ryno1234.,
Thanks for explaining more about your use-case.
I will discuss this with my team and get back to you.
Hey @ryno1234.,
We want to work with you to build a solution that fits your use-case whilst not compromising security.
The big downside to accepting a URL is that we would have to update our content security policy (CSP) to allow it to load images from anywhere on the internet.
It also means we have zero control over the size of the asset they are linking to.
This is something we cannot consider as the security risks are too high.
We are all for accepting images via API, but permanently linking out to an external url doesn’t sit comfortably with us.
We are considering a solution where you can upload file via API
In your case, your organisations would have to upload a logo file (rather than a URL), and post the file to the respective API endpoint.
Would this solve your use-case?
Yes, it would. The logo can only change through our system, so we would then just make an API call to Kinde. This is an important feature for us. Thanks!
Awesome, let me speak to my team and get back to you on this.