Could someone please give me a hand with my installation of mrbs on a school intranet site? Never really used IIS 7 before and I certainly won't be using it again! I am more used to using apache and to be honest it is much easier.
I have installed php and myphpadmin on to the server. I the proceeded to copy all of the mrbs folder on to the site directory and renamed the folder "booking" I then created the database in myphpadmin and created the tables within the database.
I navigated through to the address (http://intranet/booking/web/index.php) which asked me to change the php config file for the time (Configuration error: $timezone has not been set.) I changed this by removing the // in the php config file but I am now getting this error:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
Is there something I have missed or possibly something I need to do on the IIS server?
Here is the Authentication section from my config.inc.php
/*********************************************** * Authentication settings - read AUTHENTICATION
$auth["session"] = "nt"; // How to get and keep the user ID. One of
// "http" "php" "cookie" "ip" "host" "nt" "omni"
$auth["type"] = "ldap"; // How to validate the user/password. One of "none"
// "config" "db" "db_ext" "pop3" "imap" "ldap" "nis"
// "nw" "ext".
// Configuration parameters for 'cookie' session scheme
// The encryption secret key for the session tokens. You are strongly
// advised to change this if you use this session scheme
$auth["session_cookie"]["secret"] = "This isn't a very good secret!";
// The expiry time of a session, in seconds. Set to 0 to use session cookies
$auth["session_cookie"]["session_expire_time"] = (60*60*24*30); // 30 days
// Whether to include the user's IP address in their session cookie.
// Increases security, but could cause problems with proxies/dynamic IP
$auth["session_cookie"]["include_ip"] = TRUE;
// Configuration parameters for 'php' session scheme
// The expiry time of a session, in seconds
// N.B. Long session expiry times rely on PHP not retiring the session
// on the server too early. If you only want session cookies to be used,
// set this to 0.
$auth["session_php"]["session_expire_time"] = (60*60*24*30); // 30 days
// Cookie path override. If this value is set it will be used by the
// 'php' and 'cookie' session schemes to override the default behaviour
// of automatically determining the cookie path to use
//$cookie_path_override = '/mrbs/';
// The list of administrators (can modify other peoples settings).
// This list is not needed when using the 'db' authentication scheme EXCEPT
// when upgrading from a pre-MRBS 1.4.2 system that used db authentication.
// Pre-1.4.2 the 'db' authentication scheme did need this list. When running
// edit_users.php for the first time in a 1.4.2 system or later, with an existing
// users list in the database, the system will automatically add a field to
// the table for access rights and give admin rights to those users in the database
// for whom admin rights are defined here. After that this list is ignored.
unset($auth["admin"]); // Include this when copying to config.inc.php
$auth["admin"] = "127.0.0.1"; // localhost IP address. Useful with IP sessions.
$auth["admin"] = "administrator"; // A user name from the user list. Useful
// with most other session schemes.
$auth["admin"] = "mjf";
$auth["admin"] = "eac";
The $auth["session"] variable is the important one here. It gets the user id from the logged on users windows account the ["type"] variable is obsolete with this method so can be ignored
The $auth["admin"] variable can be set with the usernames you want to have as admin users.
Is IIS select your directory for MRBS and add application if you haven't already and set this to an integrated pipeline .NET 2 application.
You'll need to change the authentication method to windows and turn off extended protection in the advanced settings.
Bit of a faff but I couldn't get ldap to work effectively enough and this eliminates the need for the staff to have to remember to use their windows login again to get in to the system (yes they struggle with single sign on too).