After a bit of experimentation it turns out that Category Management is a Right specifically to allow creating and modifying Categories, however it does not control the ability to work with Keywords within. Permissions on the Category control what groups can RWDL Keywords.
So to prevent a group from being able to create or modify Categories while still ...
The IQ Combined Services (Index and Query) are designed to work with Elastic Search present in the DXD Stack. Index service indexes the data in Elastic Search and Query Service is used to query the data out of the Elastic Search. Both the services operate on the same Elastic Search instance.
Currently, Index Service doesn't support OAuth authentication but ...
The Content Manager Explorer, starting with SDL Tridion 2013, uses the Core Service for all of its functionality, including authorization.
Restarting Tridion Content Manager Service Host on the CMS made the setting work so that the next client browser refresh showed a limited set of folders.
Absolutely Nick, per the documentation
To add a Keyword (to a Category or Keyword), you must have Category Management rights and Write permissions for the Category.
Similar applies for editing/deleting keywords also.
To move or delete a Keyword, you must have Category Management rights and Delete permissions for the Category.
To cut and ...
The authentication is done with an API key. This key is set on the Translation settings on the source publication in Tridion.
Without this API key it is not possible to setup translation in the CMS server. And I think we can assume the TMS server will not accept requests without an API key.
If Peter is correct, my answer makes no sense of course! I will leave it for now until Hiren has confirmed that the group memberships are indeed expanded automatically.
As far as I know, the only way to do this is to go through the group memberships recursively. For example (untested code!!)
TrusteeData trustee = (TrusteeData) ...
The access to items in a folder is controlled by either the folder itself, or by the folder it inherits from. If you have permissions set locally in a child folder that allow access, the user will be able to use those items, even if the settings on the parent folder would make it difficult for them to navigate there.
So it's quite common to have - as you ...
From SDL Tridion 2011 SP1 HR1 onwards you could use a BinaryContentProvider. With this extension point you can implement your own logic to handle external URLs on multimedia components. Here you can implement your own logic to authenticate and download the media.
This is documented in the TOM.NET API documentation in the IBinaryContentProvider. Also see the ...
Detailed description of Roles is documented here.
registration user is used only for registering capabilities in discovery service.
When setting up topology, you need to use cmuser Reference here
For retrieving content (CD side), you should be using cduser
Also you can check this on Roles
It sounds to me like you are running into the infamous 'loopback' issue that occurs when the local machine name doesn't match the fully-qualified domain name (or indeed the custom host header you use).
Try disabling the loopback check by following the directions on this Microsoft KB page: https://support.microsoft.com/en-us/kb/896861
Rather than changing the Permissions on the Component/Folder, you could consider using the ElevatePrivileges and RestorePrivileges Core Service methods to elevate the user to a System Administrator during that session.
The second error is an expected one, you are trying to read the Categories and Keywords node, which isn't an Organizational item, it is just a node in the navigation tree. You can see that in the CME, as there are no properties for that node. So you are also unable to set rights and permissions on that, you have to set these on each Category separately.
The only permission needed is translation management rights on one of the target languages - they do not need any permissions on the items in the job. The reasons it mentions you need "one other right" is because TM is an extension of CM. And if you do not have a single CM right then CM will hide the publication from you as it does not see the TM right.
SDL Tridion does not do its own authentication, that is delegated to IIS. The same thing counts for when you are accessing SDL Tridion through WebDAV, as the WebDAV server also authenticates the user via IIS.
After a user is authenticated, SDL Tridion handles authorization based on what is configured for that user. If the logged in user has no read rights ...
The screenshot helps a lot in identifying the issue here, it has nothing to do with a timeout really. The issue is a misunderstanding in how the add user dialog works.
As documented (http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-C5616183-B4F1-4138-B9A7-F8D67692743B):
In Step 1 of the wizard, select users to add:
Select the value ...
The Applicable Actions are not used to drive the authorization logic in the CM Kernel, but only to drive which actions are allowed/disallowed/disabled in the GUI.
So, an approach can be to use standard CM Security to restrict access in the most lax manner and then use a Load event handler to modify ApplicableActions so that the GUI can disallow actions even ...