You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "BJ Freeman (Commented) (JIRA)" <ji...@apache.org> on 2011/10/19 12:46:10 UTC

[jira] [Commented] (OFBIZ-4489) username cannot be assign security permission

    [ https://issues.apache.org/jira/browse/OFBIZ-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130502#comment-13130502 ] 

BJ Freeman commented on OFBIZ-4489:
-----------------------------------

#1 can be simulated with the Ant command to create an admin.
It will not show up on any UI except Webtools viewing the Userlogin entity. This is the only way presently to add security and a partyID.
I am trying to think of a business case this would be needed.

                
> 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