Hi Penny,

Although DNN uses the ASP.NET membership system, it extends it in several ways that will likely make use of this interface impractical.  For example, all DNN users -- regardless of portal affiliation -- are stored under the same ASP.NET application identifier.  This means that all users across all portals would be listed within the Hero UI.  Further, DNN-specific user extensions would be inaccessible through the interface.

Although it perhaps might be possible to kludge some sort of working system together via some sort of custom hybrid provider, consider that the DNN core team (presumably) thought very hard before choosing to extend the ASP.NET membership system.  That they were unable to stick with a vanilla version strongly indicates that your doing so would be fraught with difficulty.

Hope this helps!

Brandon