[
https://issues.apache.org/jira/browse/RAVE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184369#comment-13184369
]
Jesse Ciancetta commented on RAVE-420:
--------------------------------------
Right -- I'd noticed that too -- the current implementation of
NewAccountService.createNewAccount(...) requires a non-null password to be set
in the new user passed in, otherwise I think you'll likely end up with a null
pointer. However for the use case we have which inspired this JIRA ticket that
was fine though because we're setting the password to a random value -- leaving
it blank just didn't seem right (even though we also disabled the spring
security components which support forms based login)...
Would you still rather have the ability to leave it blank though?
> NewAccountService should allow for creating new accounts which do not include
> an email
> --------------------------------------------------------------------------------------
>
> Key: RAVE-420
> URL: https://issues.apache.org/jira/browse/RAVE-420
> Project: Rave
> Issue Type: Improvement
> Reporter: Jesse Ciancetta
> Assignee: Jesse Ciancetta
> Fix For: 0.8-INCUBATING
>
>
> NewAccountService should allow for creating new accounts which do not include
> an email. This is useful for implementors who are storing the bulk of the
> users profile data in an alternate store but still need to get a stub account
> into Rave with just the username (so that all the rest of the entities have
> something to get tied to in the database).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
