Condense 'first_name' and 'last_name' to 'name'.

[graft]

Currently Janus maintains a 'first_name' and 'last_name' field for users - why? Not all names follow this schema, and it's uncommon (never?) that we want these two items separately anyway. They also clutter up the JWT (two header fields instead of 1) and end up being concatenated in many clients anyway. They should be condensed into a single field.

[jasondcater]

Think about leaving this the way it is and supporting first and last name across mount enta. It will help with user management.

[graft]

I'm not sure it's helpful, and it doesn't allow you, for example, to support users who want to use a middle initial, include a second last name, suffix, etc.

[graft]

Revisiting this, @jasondcater what are the use cases in which separate names are important? I can only think of perhaps for address (Dear Saurabh, your account is expiring), which could also be accomplished by parsing a name field. Are there other important uses you can think of?