Picking this up again - In reality, this is probably one of the things that is creating us/me the most headaches these days. Maybe I am not the only one?
While there is no norm/specification that I could find (see above, but maybe this has changed already), I have tried many different 2FA apps and while most of them give the option to rename a 2FA provider after setting it up, the reality is that most users do not know how and/or do not bother doing this.
Beside the logo (which all in all could stay the generic Cloudron logo) the "preset" name is really what is confusing most users, when the rest of a given cloudron instance is "branded".
For example:
-
Say a cloudron server is branded "Clawmazing" and the cloudron dashboard is located at my.clawmazing.ai, setting up 2FA in most application will be setup as "Cloudron my.clawmazing.ai" (and because of limited screen space, more often than not will only show "Cloudron my...")
For an end user that has no knowledge of what Cloudron is, it is very confusing and upon next login, 9 times out of 10, the user will not remember where/what is the related 2FA code to enter.
My question today is: where do most of these 2FA apps get these "Cloudron" references from which are being used in setting up 2FA in apps?
If this is not from the URL and not from the server name (because the "Cloudron Name" has been changed in the appearance > Branding page/settings of the server) then where from?
Hopefully, from the moment that this is identified, there will be ways to change this and make it match the Branded "Cloudron name" from the server instance, thus removing or very much decreasing the end user's confusion.
I am hoping that this makes sense.
