Changes between Version 7 and Version 8 of Internal/LoginService

Timestamp:

Jun 21, 2011, 3:18:49 PM (14 years ago)

Author:

Olivera Tosic

Comment:

—

Internal/LoginService

@@ -47 +47 @@
  === Database ===
 Currently, it is necessary to run sql script to create database. Resources table need to be fill out with data manually.
+
 Example:
 INSERT into resources (machid,name,location,rphone,notes,minRes,maxRes) VALUES
 ('sc1431b400c5f130', 'grid', 'Orbit Facility', '(732) 932-6857, 'Main 400 node grid,30,120)
+machid – unique resource identifier 
+name – resource name
+rphone – phone number
+notes – resource description
+minRes – minimal reservation length
+maxRes – maximal reservation length
+
+How to access login service
+
+
+1. Scheduler: 
+        https://<server_name>/schedule/
+        this is how scheduler is mapped in default-ssl. This is not obligatory, so it is possible to change this link. But, it is necessary to keep “/loginService” link name
+
+2. ControlPanel – for administrators; to View, Approve and Delete reservation, to Administrate Users and Groups etc.
+        https://<server_name>/loginService/ControlPanel
+        
+3. User Registration
+        http://<server_name>/userManagement/register
+        ( userManagement same as one in login.yaml and apache default)
+4. Group/Organization Registration
+        http://<server_name>/userManagement/orgReg 
+        ( userManagement same as one in login.yaml and apache default)
+
+
+Note:
+There is file /usr/share/omf-aggmgr-5.2/omf-aggmgr/public_html/template/ogs_login/orbit_banner.png, used for user management pages. Replace content of that file to show your logo.