Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > Developers' Forum

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 7th December 2011, 00:21
nveid nveid is offline
Member
 
Join Date: Jan 2006
Location: Daytona Beach, FL
Posts: 87
Thanks: 7
Thanked 17 Times in 14 Posts
Send a message via Yahoo to nveid Send a message via Skype™ to nveid
Default Proposed Suspend Functionality with Remote Calls

I'm thinking of adding this functionality.. Basically, the idea is similar to other panels, whereas we can standardize the 'suspending' process and have it centralized in ISPConfig code..

Here's the basic required process I'm thinking.. Input welcome:
1. Set Account Inactive, whereas they can't login to ISPConfig
2. Place Suspension page into their directory.. Rename any existing htaccess if there is any to another location. Redirect All traffic to suspension page.
3. Lock out all shell actual unix accounts using usermod -L..
4. mysql ftp accounts set 'active' field to 0.
5. Remove login permission from all mysql accounts owned by user.


Am I missing anything? And any input on where the actual 'suspend' command should be located? A remote API call is definitely a requirement in my opinion as well, so any calls in that use a suspend functionality would be standardized.
__________________
-- RLB
Reply With Quote
Sponsored Links
  #2  
Old 7th December 2011, 09:51
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,717
Thanks: 820
Thanked 5,322 Times in 4,175 Posts
 
Default

Such a functionality would consist of several parts.

A interface script which provides the form and updates the active status fields of all involved database tables, it could be e.g. located under tools.

Setting the active fields to inactive will do most of the job already as the existing server plugins will then deactivate shell users, mysql databases etc.

Routing traffic to a suspension page should be optional and configurable as many providers might want to disable a website without routing some traffic. So the change of .htaccess file should be implemented as action in the remoteaction_core_module.inc.php file so that it can be called from the interface. The website should not be deactivated in the case that you want to route traffic.


The remote api call will be the last part as its is only a function with a few lines of code that makes the internal functionality available to remote calls.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
haproxy with stunnel problem abubin Server Operation 6 10th April 2012 15:08
[Info] Remote Desktop Solutions for Linux mar.and65 Desktop Operation 0 27th April 2011 07:05
Remote frameworks fail suspend web without error yudohartono Developers' Forum 0 21st March 2011 11:26
remote framework - is it customer or admin side? alipanick Developers' Forum 2 8th October 2009 20:35
Newb: Result of nessus scan Slowhand Installation/Configuration 12 4th June 2009 15:31


All times are GMT +2. The time now is 13:57.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.