[
https://issues.apache.org/jira/browse/OFBIZ-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131908#comment-13131908
]
BJ Freeman commented on OFBIZ-4489:
-----------------------------------
#2 you can create a defualt Party or PartyGroup that all logins you might
created ths way.
The usng the drop down or lookup for partyID that would be added you can select
that partyID.
This then allows the login to appear in the Selected ParrtyID, and you can then
modify/add security and roles..
This also make it easier to maintain the login for a particular function.
> username cannot be assign security permission
> ---------------------------------------------
>
> Key: OFBIZ-4489
> URL: https://issues.apache.org/jira/browse/OFBIZ-4489
> Project: OFBiz
> Issue Type: Bug
> Components: party
> Affects Versions: SVN trunk
> Reporter: Wai
>
> PartyMgr permits the creation of a new username(or userLogin) without being
> associated with a party/partygroup. As a result, the new username cannot be
> assign to a securitygroup and hence cannot be used to access the system.
> Possible solution:
> 1. Fix code to allow a party-less username to be assigned to a securitygroup.
> 2. All created username must be associated with a party.
> Reference discussion about this issue:
> http://ofbiz.135035.n4.nabble.com/creating-a-new-user-login-td3905814.html
--
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
