for a project on which I work, we would like an admin user to be added to the database at the start of the first deployment automatically because for the moment it is done manually. if you have tips please share them with me
Related
I've built an app in App Maker and deployed it, but the user I thought I had given permission to is getting this notification "Sorry, you don't have access to this application."
In the app, I added a role to the data source and added the user to the role from the deployment. I also added the role to each page's security. I verified that App Maker is turned on for all of our users. I've ensured that the user has access to the Google Sheet data tables (both what I imported into the App for preview and the data I exported from the deployment). I've even added the user as a Cloud Sql Viewer in our Cloud SQL instance (don't know if that was necessary). This is my first app and I feel like I'm flying blind. I'm obviously missing something but can't figure out what. Any help is much appreciated!
Make sure all the required models can be accessed by the role you assigned to the user.
If the user has another Google account in the same Chrome session, the browser may be switching them to this external user when opening the app. Sign-out from that account or try incognito.
Make sure the deployment has no restriction as shown here; or if it does, allow the username.
i'm quite new to Firebase and currently having some trouble trying to implement a custom role for my project. Is there a way to set a role with only Database permissions (add and delete) and another one responsible only for Authentication? Thanks in advance!
This level of granular access control is being rolled out in the Firebase console right now. If your project has it, you'll find it by:
Click the ⚙︎ at the top left.
Click Users and permissions.
Click the row of the user who's permission you want to change.
Click the Roles dropdown.
Click Assign Firebase roles
Select the roles you want to give to the user.
You'll note that the database role is still less granular than what you want, you can simply allow the user to edit the database or not.
You can customise access from project settings in firebase console.
Search for settings icon at upper left corner and then go to project settings. There will be some option of users from where you can customise access.
I'm trying to limit the ability for user accounts to be created. My host has noticed spam activity on my account and has suggested that it is being generated by accessing the user account creation script directly.
When I try to access that feature in Drupal 7, the Setting tab doesn't render correctly. Fields and Display tabs function correctly.
Screen Snap
If your host is right about the script being accessed directly, then your site might be hacked.
Since you also have problems with rendering of the settings tab, I would execute these steps in this order:
Follow the instructions for updating Drupal, starting with backup of
the database and the files:
https://www.drupal.org/docs/7/updating-your-drupal-site/update-procedure-minor-version-change
Set secure permissions for files and folders: https://www.drupal.org/node/244924
The second step alone might help stopping the user creation by direct access to the script, but it will not get back the original settings tab.
In back-end go to Configuration -> People -> Account settings. There is a section Registration and cancellation and Who can register radio buttons group where you can forbid anonymous user create account. If that's already set well and people are still registering then it really is possible that your site has been hacked.
We are using Plone 4.2.2 and we would like to delegate user account/group creation and managing local roles on content to our tier 1 helpdesk folks. We initially thought to use the Site Administrator role and just add the Site Setup Overview and Site Setup Users and Groups permissions. This allows them to create users and groups, but they don't have access to the sharing tab to manage local roles on folder and file objects.
I'm not finding much help out there and this seems like it would be a fairly common delegation. In fact, I'm surprised there isn't a role specifically for this. Giving Manager role to our tier 1 is a little scary.
Any suggestions would be greatly appreciated.
I found this thread that referenced Managing Users, but not the local roles on content
How to create a Plone 4 group who's sole purpose is to manage users?
The access to the sharing tab is only about permission.
You must give to your users the "Sharing page: Delegate roles" and all needed permission named "Sharing page: Delegate XXX role".
But to be honest I think that the Site Administrator role already have all those power you need.
What I would do is that instead of using the normal Plone user manager I'd
write a custom, simplified, user management form in Python add-on
form does sanity checks by allowing creating only of certain kind of users with certain roles
form also can delegate setting local roles on folders programmatically (no need to go to Sharing tab)
expose this form through a special new permission
Give the permission for the form to Tier 1 support personnel
As the use case is very specialized it might be easier to write your own manager form than customizing existing Plone logic.
i'd like to create a Unique Web Site Administration Tool (UWSAT) to admin all users for all my websites on production server.
Basically the idea is to have the UWSAT with only an admin user; when the admin log the tool he could navigate the applications, select one and see its users . He could add new user to an existing application, or create a user specifying a new application name (as far as i know that create the application too).
The problem i'm facing is that to add a user to an application i have to set the Membership.ApplicationName but i read this should be avoided.
So i ask you : should i create a different MembershipProvider for each application and call it when i have to manage users for that application?
Thanks.
I recommend creating a role, and assigning it to the users. The role would be the application they should have access to.
The RoleProvider is one way to do this.