> What I've done here is a "link" between my customizations and the identity > default tables... This way I don't have to repeat any structure and I know > that all users I have on my system are also user with regards to the identiy > part.
There was some talk of using a SingleJoin to link the base Identity tables with custom ones to "extend" them, though for my application replacing them works fine too. Only issue I'm running into is wildly different naming schemes - being able to override the name of the "userId" field would be nice, as my application uses full e-mail addresses.
