Named rights in Adobe Campaign Classic | Community
Skip to main content
W
WesleyXPL
Level 2
August 6, 2020
Solved

Named rights in Adobe Campaign Classic

  • August 6, 2020
  • 1 reply
  • 2489 views

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

 

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jonathon_wodnicki

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

 

1 reply

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
August 6, 2020

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

 

rahulkad29786
rahulkad29786
Level 4
February 3, 2022

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

 

D
dipendu_g
Level 5
October 2, 2024

Hi @rahulkad29786,

 

Were you able to figure out a way, on this, if you please share

 

Regards,

Dipendu

Terms & ConditionsAccessibility statement

Loading footer...