Versions Compared

Old Version 4

changes.mady.by.user Unknown User (adrianc@hlmksw.com)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (adrianc@hlmksw.com)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

New Design Implementation Example

This description includes permission expressions that are in the form of ArtifactIdentifier\[PermissionsList\]. The expressions are illustrative - they are not intended to be some kind of "permission string." How permissions are stored and managed depends upon the Authorization Manager implementation.

Info

Wiki Markup

There is no permission checking code in the contact mechanism service definitions or in the screen widgets. The existing partyIdPermissionCheck service is used to check if the user equals the contact mechanism party (it would be helpful to rename the service userEqualsParty or userIsParty).

...

Using the static artifact hierarchyunmigrated-wiki-markup

OFBiz/party/service/createPartyPostalAddress\[access=true, service=partyIdPermissionCheck\]
OFBiz/party/service/updatePartyPostalAddress\[access=true, service=partyIdPermissionCheck\]
(nine more contact mechanism service artifacts with the same permission list)
OFBiz/party/screen/viewProfile\[view=true\]
OFBiz/party/screen/editcontactmech\[view=true, create=true, update=true, service=partyIdPermissionCheck\]

Using the dynamic artifact hierarchy

Wiki MarkupOFBiz/party/party/partymgr/createPartyPostalAddress\[access=true, service=partyIdPermissionCheck\]
OFBiz/party/party/partymgr/updatePartyPostalAddress\[access=true, service=partyIdPermissionCheck\]
(nine more contact mechanism controller request artifacts with the same permission list)
OFBiz/party/party/partymgr/viewProfile\[view=true\]
OFBiz/party/party/partymgr/editcontactmech\[view=true, create=true, update=true, service=partyIdPermissionCheck\]