[
https://issues.apache.org/jira/browse/OFBIZ-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213435#comment-14213435
]
Mridul Pathak commented on OFBIZ-4489:
--------------------------------------
This is an invalid issue, OFBiz does have option available to assign security
permissions to a userlogin even if it is not tied to a party. Steps for this
are,
# Go to http://demo-trunk-ofbiz.apache.org/partymgr/control/FindUserLogin
# Select "system" user login, which is not tied to any party
# Go to "Security Groups" tab,
http://demo-trunk-ofbiz.apache.org/partymgr/control/EditUserLoginSecurityGroups?userLoginId=system
# You could now assign security permissions directly to the user login
# There is also an option to create new user login without tying it to a party
at http://demo-trunk-ofbiz.apache.org/partymgr/control/FindUserLogin.
The above option is available in all of 12.04, 13.07 and Trunk. This issue
could be closed now.
> 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: 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 was sent by Atlassian JIRA
(v6.3.4#6332)
