Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Named rights in Adobe Campaign Classic

Avatar

Level 2

Hi,

 

We're trying to limit the number of operators with administrator clearance. However, it seems like lot's of functionalities actually require administrator rights, which isn't okay.

 

Therefore we are wondering if we can create a specific named rights for the following two actions so that we can assign those two rights to the operator groups needing them, and thus preventing those operators from having access to everything:

  • Offer validation
  • Package management
    We are aware package management is usually done by admins, but in our case it's not feasible.

Is there anyone knowing if this is possible and if so, how this can be achieved?

 

Wesley

 

 

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi,

 

A package management right would effectively grant root access, e.g. a user could make a package:

<package author="Z3r0 c00l" buildNumber="1" buildVersion="6.7">
  <entities schema="xtk:operatorGroup">
    <operatorGroup>
      <group name="admin"/>
      <operator name="myselfThanks"/>
    </operatorGroup>
  </entities>
</package>

And upgrade their account without any real effort.

 

So with security removed as a requirement, it's a matter altering the UI to check for the new rights:

  • Navigation hierarchy for package import menu item, HasNamedRight('PACKAGE_IMPORT')
  • JSSP/js lib for offer validation

 

Thanks,

-Jon

 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi,

 

A package management right would effectively grant root access, e.g. a user could make a package:

<package author="Z3r0 c00l" buildNumber="1" buildVersion="6.7">
  <entities schema="xtk:operatorGroup">
    <operatorGroup>
      <group name="admin"/>
      <operator name="myselfThanks"/>
    </operatorGroup>
  </entities>
</package>

And upgrade their account without any real effort.

 

So with security removed as a requirement, it's a matter altering the UI to check for the new rights:

  • Navigation hierarchy for package import menu item, HasNamedRight('PACKAGE_IMPORT')
  • JSSP/js lib for offer validation

 

Thanks,

-Jon

 

Avatar

Level 3

Hi Jon,

I have also a similar kind of requirement where we need to provide only package creation access to few users but do not want them to be admins on the same side.

Was going through answer post above, but still not able to get clear the last point you mentioned i.e.

"So with security removed as a requirement, it's a matter altering the UI to check for the new rights:

Navigation hierarchy for package import menu item, HasNamedRight('PACKAGE_IMPORT')"
so are you referring here to creation to a new named right? or is getting only package mgmnt right is not possible?
will appreciate your detail response.
Thanks