7
votes
Accepted
Version of Tomcat embedded with Tridion 8.5
There is a hotfix that updates all microservices to use Tomcat version 8.5.13. - see http://csei.sdl.com/hotfixes/#/hotfixes/c, and search for hotfix CD_8.5.0.4115
I'm not sure if the CM uses some ...
5
votes
Accepted
Automatically logging out SDL Web 8 user from the CME after X hours
There will be two step process:
Create javascript file which can detect idle time. Refer following link for this implementation: Detect idle time in
javascript
Load this javascript in ...
4
votes
Accepted
Can we give Folder or Structure Group level Access to Users and Groups
Yes, this permission granularity is something that Tridion provides out of the box.
For example, the screenshot below shows the permissions for the 800 Author group on a specific folder:
You can set ...
4
votes
Accepted
2
votes
Get a list of valid users and groups for for a specific component or page
I have implemented the same type of feature in my project.
Here are the steps that I have followed -
First read the all the tasks from that workflow process.
Then read the group involved in that ...
2
votes
How to implement/hack security on SmartTarget promotions?
This was pretty easy to achieve with a GUI Extension Data Extender, which filtered the lists of regions and promotions sent from the CMS to the SmartTarget GUI.
I used normal Tridion Group ...
2
votes
Restrict Publishing by User to Target in Same Publication
The answer you probably don't want to hear is, "Port those structure groups and pages to a separate publication!" ;)
1
vote
Restrict Publishing by User to Target in Same Publication
Another approach that can be used is event system where you can capture publish transaction verify the structured group and decide whether to publish or not.
The reference for such implementation is ...
1
vote
Restrict Publishing by User to Target in Same Publication
The best OOTB solution would be to use Tridion security and educate the users. Custom resolver, like you highlighted, is another technical solution that would work really well.
You could also create ...
1
vote
Restrict Publishing by User to Target in Same Publication
I would have used Publication Metadata to configure which items should go where. You can enable "key-value" pairs via metadata schema to specify which target should pick up which SG or items from an ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
security × 262011 × 4
user-management × 4
permissions × 4
cme × 3
2013 × 2
content-delivery × 2
workflow × 2
ecl × 2
ldap × 2
user-rights × 2
2013-sp1 × 1
web8.5 × 1
web8 × 1
core-service × 1
publishing × 1
gui-extensions × 1
content-manager × 1
smarttarget × 1
2011-sp1 × 1
configuration × 1
content-porter-2013 × 1
odata × 1
ambient-data-framework × 1
content-porter-2009 × 1