I am trying to create a separate subdomain for an administrator to edit their webpage, like admin.example.com
in cPanel, I created a subdirectory called admin and it automatically created a root directory under /public_html/admin. I password protected the directory and it works great. It also brings up the password prompt when I go to example.com/admin. I know its because it created the /admin directory, but is there a way to only access it through admin.example.com? I might just be picky, but I'm curious.
I'm creating a very tiny cms for a client to update a few areas on his site and was wondering whats the best way for him to access the admin/edit page? Is a password protected example.com/admin directory ok? Or is a subdomain better? Or something else?
Both example.com/admin and admin.example.com are password protected. For a tiny CMS this security is enough.
Related
My target site needs AD auth to browse and use the admin portal. All is fine there. This means syncing to this server via username and password authentication doesn't work. Does this mean i need to enable x.509 authentication?
If you mean using the Staging Module, the staging module's "Username and password" really is not linked to the actual CMS Users. You can put whatever Username and Password on the Destination server, and connect to it from the Source.
x.509 is also fine.
Tell me if you aren't talking about the Staging Module though.
You may need to do 1 of 2 things:
Enable mixed mode authentication. Yes the overall authentication doesn't need to use a physical cms_user user but since you have AD Authentication enabled, anytime another user or service tries to access a system page it may require them to log in.
Create a web.config location node in your /CMSPages/Staging/web.config file that excludes anyone or everyone to access a the SyncServer.asmx page within there.
Otherwise configure the x.509 certificate setup.
Our website is on a shared server and we can change file and directory permissions using cPanel. What are the recommended permissions for the IPN Listener and the IPN Log file?
Currently, they are both set to "0644". However, the Log text file can be viewed through a web browser if you know the URL, which can't be good. I don't see any recommendations on PayPal for this.
I did see an older post that mentioned 0755 for the Listener. Is this still recommended?
File permissions generally don't correlate with whether people can access your files through the web. Permissions only relate to what users and programs on the local server can access the file how.
The ideal permissions would be the minimum required for the web server to serve the file, and for you to be able to upload/edit it.
644 is very common I think, but because it's a shared server, I'd check with the server administrator for the optimal setting.
If you have a log text file that you don't want to be viewed through the web, the safest way is definitely to place it outside the web root.
Is there anyway we can restore a complete (or partial, but with the email settings intact) cpanel backup to a new account without the help of WHM?.
I have two reseller accounts - shared (hostgator). Have already downloaded the entire files (/ssl, /ftp, /mail, /public_html etc. ) using FTP from account 1.
Also created an account in 2nd hosting package with the same domain, username and password. Will it work if I upload all the files to the new server?.
Please note: I dont have root access also.
Yes, You can restore your account files through "Backup Wizard" feature. With this feature you can restore your partial backup zip file(s).
Please check it : https://documentation.cpanel.net/display/ALD/Backup+Wizard#BackupWizard-PartialBackup
I have a application .net that search a folder on report server and reads the reports inside that folder and display on asp.net page. The permissions for the asp.net user are working fine to deploy and execute on website.
Now, I want to users to deploy on "My reports" folder, so they only see theirs reports.(The users have access to report server and use report builder).
I search and I could not find a solution for this:
I want to give permissions to an a user (the same that is running on asp.net server), to access all "My reports" folder of all users(Users Folder), so I can execute the reports inside users folder on website.
I put the asp.net server user as local administrator of the report server, but with that permission te user can only see the content of the folder, this user can not execute the report. Any idea what is the problem?
I finally found a solution, and does not involve add users to local administrator of the machine.
I used the IAuthorizationExtension.
I found this example that enable anonymous access for all users witch was a start.
On my implementation I used WindowsAuthorization, because I want to keep the existing authorization and give access to one specific user. On all CheckAccess methods I check if the user is the one I want to give access and return true otherwise return the WindowsAuthorization.CheckAccess(...). On all others methods of the interface I also used the WindowsAuthorization.
With this solution the user running website can access all content of reporting services.
I am building a site using ASP.NET MVC 2. The site itself needs to be public but the admin section should require a windows login and the user logging in needs to have local admin privileges on the server.
i.e. http://server/site should be open, but http://server/site/admin should force an admin login before proceeding.
Can this be done in code or by tweaking the web.config file? If necessary, making configuration changes to IIS is acceptable but I am trying to keep deployment steps down to a minimum.
I don't know if you can do this in web.config, or even if it's possible via IIS in an MVC application (since /site/admin won't exist on the file system), but it is possible to have different permissions for different folders under IIS. You will need to use the IIS manager to configure this.
You may also be able to use an AuthorizeAttribute on your admin controller.
This turned out to be fairly straightforward:
Enable Windows Authentication in IIS.
Enable Windows Authentication in web.config.
Decorate each action that needs to be secure with [Authorize(Roles = "Admin")].