I run in to this block many times to figure out a way to share cpanel access with another user without having to give them my cpanel admin username/password. Is there a way to create an additional cpanel users. In this case its godaddy.com but I am wondering in general as well.
That way I do not have to share my own access.
Thanks.
As far as I know there is no other way (at least at this moment). This is a cpanel feature that would be available in WHM version 64.x
You can read more details here:
https://features.cpanel.net/topic/multiple-cpanel-logins-cpanel-subusers
For every account in cpanel environment it creates just a single user to access the cpanel administration portal , you can allocate multiple user for it.
However with FTP you can grant the access to the data if needed by creating multiple FTP user account.
As you said you are using shared hosting and in shared hosting you can not create another cpanel username/password.
But, my friend you can do one thing to (that is allow some limited access) you can create ftp account as number of ftp account allowed by hosting provider.
Your user can add/update/delete file for particular assigned directory.
Thanks
Hope! this will help you
Related
I have a "public" website deployed on azure. I want to get access only from a limited number of authorized tester persons.
I cannot use ip restriction because all of us have dynamic ip and we are dislocated all over the world.
Here the solution I have adopted, but I am not confindet is the correct.
I have enabled authentication.
I have also created users in active directory and added to my application:
Everything works. Now, before access to the website, people must login.
But... what I do not like is that people can access to portal azure with the email I have authorized on active directory. They do not see anything, but they can access into that directory. is there a way to avoid this?
Does exists a better solution to restrict access to my website?
Thank you
You can restrict access to Azure Portal with Azure AD conditional access
https://learn.microsoft.com/en-us/azure/role-based-access-control/conditional-access-azure-management
https://learn.microsoft.com/en-us/answers/questions/112173/can-we-restrict-azure-portal-httpsportalazurecom-a.html#:~:text=Yes%2C%20we%20can%20restrict%20access,Azure%20AD%20Premium%20P1%20License.&text=as%20shown%20below%3A-,Navigate%20to%20Azure%20Portal%20%3E%20Azure%20Active%20Directory%20%3E%20Security%20%3E%20Conditional,and%20Groups%20%3A%20Select%20required%20users.
I want to give read-write access to a specific folder in Azure VM to someone from his/her machine at home. I do not want him to give access to login to the machine, but some way so he/she can reach the directory and make changes. Any ideas?
I do not want him to give access to login to the machine, but some way
so he/she can reach the directory and make changes. Any ideas?
According to your description, maybe we can deploy FTP on that VM. In this way, he/she can access this folder on internet, we can give them read-write permission.
Here a similar case about how to deploy FTP on windows server, please refer to it.
On a fresh CentOS application;
How can I create a separate user other than root, to store the
website hosting files?
How can I lock this user down to prevent malicious or bad things from happening?
How can I further protect the php file containing the DB connection strings?
What other security measures shall I take to protect a such server which is only used to server a web-app? (or two)
What other ways shall I employ for sand-boxing the web-app?
I am running Centos on a VPS and want to use Apache or Lighttpd as the web server.
Thank you.
One best practice is always to only run services you actually need on a box facing the internet. So if you only need apache and a database, run only apache and the database on that machine. Long, random passwords for maintenance user, do not allow direct root login.
Regarding the user: add a user with useradd and block shell access for that user (usermod -s, set login shell to /sbin/nologin). Usually a service account for running the web server is created after installing the web server. If you restrict permissions for that account to the web server home and logging directories, you should be fine.
Regarding protecting the database: you can create a db user account that doesn't have drop or create privileges, but as your application needs access to the database, someone acting with the privileges of your web server or application will have access to the data in the database as well.
I am learning how to setup a shared hosting web server.
As a server administrator whose the highest access level in the server, I want to grant my friends as site administrators access to their own sites.
The question is:
What is the best way to setup their accounts and what level of access should be granted to them?
Edit 1:
I want them to have remote access to their own resources using IIS Manager. By this way, I can mimic a real shared-hosting server.
You can install a FTP server. And assign the permission to access a folder for a user with user name and password.
Use the delegated administration on IIS.
I have a SharePoint virtual machine in one active directory domain (for example domain1) and I want to transfer all the sites it has to another active directory domain (domain2).
I don’t know which could be the best procedure to do this, if I detach and attach my virtual machine from domain1 to domain2 it probably didn’t work since all the accounts used by SharePoint are no longer valid. (Both domain are not in the same network and didn’t trust each other).
Additionally I could export the sites in domain1 and import them on domain2 using stsadm, but if I use this technique I have to manually install all the features, solutions and personalization I made on my original server.
Does anybody know the best approach to “move” the sites from one domain to another?
There is a STSADM Custom Extension: move web that should be what you are looking for:
C:>stsadm -help gl-moveweb
stsadm -o gl-moveweb
Moves a web.
Parameters:
-url
-parenturl
[-haltonwarning (only considered if moving to a new site collection)]
[-haltonfatalerror (only considered if moving to a new site collection)]
[-includeusersecurity (only considered if moving to a new site collection)]
[-retainobjectidentity (only considered if moving to a new site collection)]
You may have some sucess by adding a local account to the administrators group and joining the server to the new domain. Then manualy updateing all of the AD accounts that are used in the server. I sould note that all of your users will then have new accounts that are not related to the old ones.
You sould ask your domain admins about an SID update to the new accounts so they also have the SID's from the old domain.