Amila, +1 on autogeneration without prompting user.
I think that if we have smart enough substitution rules (e.g. remove spaces and if necessary add numbers to disambiguate) the ID will be recognizable enough, and also - to your point - indeed, customers who care about URLs will use their custom URLs anyway, so our internal Customer ID will not affect them at all. Dmitry On Mon, Apr 21, 2014 at 10:05 PM, Amila Maha Arachchi <[email protected]>wrote: > Hi all, > > In the current registration model we are working for WSO2 Cloud, we are > registering the user with the email. Then when we are creating the tenant, > we prompt the user for a display name and a company id. This display name > will be used in all the UIs and company id (which will be taken as the > tenant domain) will be used in functional stuff. > > There is a suggestion to avoid asking for a company id from the user and > generate it from the display name provided by him. > > For example, if the user provides the display name for the organisation as > "My organization", we can generate the company id (tenant domain) as > "myorg" or "myorganiz345" in a unique manner. If the user provides > something like "john.com" we can use it as it is. > > Although we are using the display name everywhere in the UI, there will be > places which display the company id such as the URLs shown in API Manager. > One disadvantage I see is, if we assign a company id in the likes of > "myorganiz345", user will find it difficult to remember a URL (unless/until > url mapping is there/not there). > > WDYT? > > Regards, > AmilaM. > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware <http://wso2.com/events/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
