I have installed Airflow in my Ubuntu system and trying to deploy Airflow to production. I would like to turn off the menu Docs on the UI (browser).
I was reading setting permissions on the menus here access-control but it is hard to turn off this menu for each role. I am curious to know if we can Disable/Hide/Remove Docs menu from the root.
There's no one-click way to turn it off globally. I wonder why it's hard to turn it off for each role? The only way to truly perform this in one action is to query the metastore directly and remove the menu access on Docs permission from all roles using a single SQL query.
Assuming you don't have too many roles, it takes just a few clicks in the UI. First you'll need Admin permissions and go to Security -> List Roles. In there, edit each role and remove the menu access on Docs permission.
Related
Using AWS I have a lot of Chrome tabs open with multiple services. When I switch between them I am constantly getting signed out. Sometimes it's a matter of just few minutes.
AWS minimum session duration is one hour, so that's probably not the problem. How can I tackle this? Getting logged out of Lambda makes it lose all the undeployed code, this is very inconvenient.
Edit:
Answering the question in a comment: I do have multiple accounts and when I want to open a tab with a new service I just click management console (screenshot) and follow on from there. It appears to cause the actual logout.
But here's the thing - I am currently using resources only from the first account. So (since I'm within one account all the time) it shouldn't log me out right?
I see this message when I use AWS one one Account, then login to a different account in a different tab. If I return to the original tab, it recognises that I am no longer logged-into the first account and asks me to reload.
It seems that you are using SSO to login and it is generating a different set of temporary SSO credentials. Instead of using that link, select the AWS service from the search field at the top of the console, then right-click the service and "Open in New Tab". That will open the other service in a new tab, using the same login credentials.
I'm trying to create my first project in google cloud with organization's administrator account. I have access to the administrator's email and passwords and I am logging in with that account to do so. The problem is that when I click on create new project I receive the following error:
There was an error while loading /home/dashboard?project=proven-now-305315&authuser=1.
You are missing at least one of the following required permissions:
Project
resourcemanager.projects.get
Check that the project ID is valid and you have permissions to access it. Learn more
Send feedback
The detail is that in my resource administration panel I already gave the permission that they ask me to the resource as shown in the following image:
As I have read, the project IAM Admin role should grant the resourcemanager.projects.get role and as you can see in the image the resource rcv # .. which is the administrator has it activated, however I keep trying to create a new project and it doesn't allow me to do it. Any idea?
In case anybody else, like me, reaches this answer, I want to point out that the accepted answer is correct, but for me I had to also make sure that within the settings, I ensured that Project Creation Settings on the right pane and under the section of Cloud Resource Manager Api Settings was set to on. It was turned off by default. Many people on my team overlooked this as it is significantly smaller text.
This may be an option that was not present before or it was turned on by default in the past. For us, it was turned off.
Please refer to the included image for a visual representation of the
settings that need to be turned on.
The problem was for some reason the Google Cloud was disable for all users, I solved following this instructions. Solved with this!
To activate this service, please follow the steps:
Access the admin console and go to Apps -> Additional Google Services
Look for the service “Google Cloud Platform” and click on the box next to it
In to top right corner click in “ON”
Confirm you want to turn it on in the pop-up box.
If I have an item in draft state and I go to Experience Editor, the add new component is disabled and I cannot add any new components for an Editor role.
Any idea where should I look?
It sounds like member Roles are the issue here.
Look into including one of the Designer roles (Designer / Sitecore Client Designing)
From Sitecore security roles documentation:
Sitecore Client Designing
Gives the user access to Experience Editor Design pane features that allow a user to set layout details associated with items in the Sitecore client.
Members of this role are: Designer
and
Designer
Gives the user read and write access to the areas of the content tree
that are required when changing layout details for individual items
and groups of items via template standard values, as well as items
required when configuring the Experience Editor Design Pane.
This role also has two of the Sitecore Client roles assigned to it, so
if you assign just this role to a user, the Sitecore Client Designing
and Sitecore Client Users roles will be automatically assigned to the
user.
This role provides access to the Experience Editor Design Pane
features and the designer options in the Content Editor.
Note This role is not a member of the Author and Authoring roles, so
it does not allow users to edit items.
Members of this role are: Developer
This sounds like a a workflow security issue. I would recommend using the Access Viewer to check the user's access to the item you are trying to edit. If it tells you that there is no access, the right side of the tool should tell you why. If the 'why' is workflow state access, you probably need to adjust your security on the Workflow state for 'Draft'.
I'm using Sitecore 7.2 and trying to allow a user to set things like datasources and some custom parameters on sublayouts in page editor mode. The user is a member of sitecore\Designer and sitecore\Author, but when that user tries to edit the component properties, the fields appear grayed out/disabled.
I am able to enable these options by setting a user as an admin, but don't want to grant quite that much power to this particular user.
Here is how tried it and it works on Sitecore 7.2
Create a new user called cbarnes (and in your case if there are other content editors)
Create a new Role - call it say SP Content Editor Authoring
Make that role a member of sitecore\Author and sitecore\Designer. This way it inherits everything from those two roles.
Make the user cbarnes one of the members of that role.
Lastly go to the security editor and give Write permission on the item after selecting the SP Content Editor Authoring Role under Roles and Users section.
Login as cbarnes user and check if it work!
Let us know if this works for you. Happy Sitecoring!
I actually ran into this same issue today on a 7.2 project. While my user had both the sitecore\Designer and sitecore\Author roles as a part of a client-specific author role I created, they were not able to edit rendering parameters.
By default, users in these roles have read-only access the Sitecore\Templates folder. Within this folder I had an additional folder named "Rendering Parameters" where I stored all my rendering parameters templates. I added Write access to the client-specific role for my "Rendering Parameters" template folder and users in that role can now edit and save rendering parameters without elevated permissions.
Use "Access Viewer" tool from Sitecore start menu to define why your user does not have required rights.
By default both roles sitecore\Designer and sitecore\Author have field read and field write access to Layout template section fields. But, it seems that roles have only read access to item that you are trying to edit. You can add write access to that item.
For more details look at Security Administrator´s Cookbook
I am working on a website that uses Sitecore CMS. An intranet webpart was already created with restricted access.
In this intranet I've created a new page which should only be visible for 1 role. I have created the new role. I tried to mess around with the security of the page in the content editor (Security --> Assign). I published the changes. But no matter what I do, it doesn't seem to have any effect.
Any guidance would be greatly appreciated!
Open the sitecore desktop ( http://yoururl/sitecore/shell ), click on the 'sitecore' button, then 'security tools' and 'security editor'.
Select the 'anonymous user' account in the ribbon, click on the chosen page in the tree, and click 'x' near 'read'.
Then click 'select' in the ribbon and choose the proper role. Once again select the chosen node and allow 'Read' rights for the role.
Once it's done, you can use 'Access viewer' app (once again sitecore button and security tools on the desktop) to check whether the rights are set properly.
The trick is probably to deny access for the extranet\Anonymous user and then grant access for the role.
I like to use the Access Viewer or the Security Editor for that, instead of the Content Editor as it gives you a better overview.
Make sure to put inheritance to good use so you don't have to set security to each item individually but rather on the root of the site (if possible).
I advice you to take a look at the Sitecore Security Administrators Cookbook: http://sdn.sitecore.net/upload/sitecore6/securityadministratorscookbook-usletter.pdf