1 / 8

Current Technical Solutions

John Eyre De Montfort University, Leicester DNER ANGEL Project partner JCIEL MLE Project ALT-C 2002, Sunderland. Current Technical Solutions. Authentication Systems Databases (R+L) LDAP SRS SMB VLE (NT, HTAccess, Unix Password, Netware). Users Web Browser. User goes to MLE web site

morrison
Télécharger la présentation

Current Technical Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. John Eyre De Montfort University, Leicester DNER ANGEL Project partner JCIEL MLE Project ALT-C 2002, Sunderland Current Technical Solutions

  2. Authentication Systems Databases (R+L) LDAP SRS SMB VLE (NT, HTAccess, Unix Password, Netware) Users Web Browser User goes to MLE web site MLE presents Login screen User enters Login details MLE checks with local LDAP MLE MLE then asks Local ANGEL ANGEL UM checks its Targets Positive reply from VLE, Includes list of Groups (Modules). Local LDAP system MLE User DB ANGEL User Manager XML Config File User Authentication Scenario 1 User is not recognised

  3. <?xml version="1.0"?> <!DOCTYPE angel:um_config SYSTEM "http://www.angel.ac.uk/dtds/UM_config.dtd"> <!-- Written by by Steve Beech (jbeech@dmu.ac.uk) --> <angel:um_config xmlns:angel="http://www.angel.ac.uk/namespace"> <!-- Configuration information for um_servers and clients --> <angel:hostname>soar.dmu.ac.uk</angel:hostname> <angel:port type="unprotected">5556</angel:port> <angel:errorlog switch="on">d:/angel/UM_errorlogfile.txt</angel:errorlog> <angel:usagelog switch="on">d:/angel/UM_usagelogfile.txt</angel:usagelog> <angel:permittedHost>soar.dmu.ac.uk</angel:permittedHost> <!-- Server specific config information --> <angel:um_server> <angel:auth_handlers> <angel:auth_handler> <angel:name>LDAPservice</angel:name> <angel:type>uk.ac.angel.um.LDAPSearch</angel:type> <angel:directoryservice>LDAPservice</angel:directoryservice> <angel:location>ldap://ldap1.dmu.ac.uk</angel:location> <angel:port type="unprotected">389</angel:port> <angel:basedn>o=dmu,c=GB</angel:basedn> <angel:class>LDAPSearch</angel:class> <angel:timeout>2000</angel:timeout> </angel:auth_handler> <angel:auth_handler> <angel:name>SMBservice</angel:name> <angel:type>uk.ac.angel.um.SMBSearch</angel:type> <angel:directoryservice>SMBservice</angel:directoryservice> <angel:location>http://smb.dmu.ac.uk</angel:location> <angel:smbserver>smb</angel:smbserver> <angel:sharedresource>shared/auth.txt</angel:sharedresource> <angel:class>SMBSearch</angel:class> <angel:timeout>2000</angel:timeout> </angel:auth_handler> … <angel:directory_service> <angel:name>QLSservice</angel:name> <angel:type>uk.ac.angel.um.QLSDirectory</angel:type> <angel:location>146.227.99.999</angel:location> <angel:port type="unprotected">9999</angel:port> <angel:timeout>2000</angel:timeout> <angel:stylesheet>c:/angel/ss1.xsl</angel:stylesheet> <angel:searchfield> <angel:matches> <angel:match> <angel:result>CC101</angel:result> <angel:group>CC101.dmu.ac.uk</angel:group> </angel:match> <angel:match> <angel:result>CC205</angel:result> <angel:group>CC205.dmu.ac.uk</angel:group> </angel:match> <angel:match> <angel:result>CSE</angel:result> <angel:group>ComputerScienceEngineering.dmu.ac.uk</angel:group> </angel:match> </angel:matches> </angel:searchfield> </angel:directory_service> … <angel:directory_service> <angel:name>QLSservice</angel:name> <angel:type>uk.ac.angel.um.QLSDirectory</angel:type> <angel:location>146.227.99.999</angel:location> <angel:port type="unprotected">9999</angel:port> <angel:timeout>2000</angel:timeout> <angel:stylesheet>c:/angel/ss1.xsl</angel:stylesheet> <angel:searchfield> <angel:matches> <angel:match> <angel:result>CC101</angel:result> <angel:group>CC101.dmu.ac.uk</angel:group> <angel:auth_handlers> <angel:auth_handler> <angel:name>LDAPservice</angel:name> <angel:type>uk.ac.angel.um.LDAPSearch</angel:type> <angel:directoryservice>LDAPservice</angel:directoryservice> <angel:location>ldap://ldap1.dmu.ac.uk</angel:location> <angel:port type="unprotected">389</angel:port> <angel:basedn>o=dmu,c=GB</angel:basedn> <angel:timeout>2000</angel:timeout> </angel:auth_handler> ANGEL User Manager - XML Configuration File

  4. Users Web Browser Academic User goes to MLE web site and queries SRS for details of students registered on his Module. The Academic then clicks the option to create and load a course/module in a specified VLE. ANGEL determines the appropriate protocols for querying the SRS and Creating accounts in the specified VLE. MLE VLE MLE User DB ANGEL User Manager The appropriate data is transferred from SRS to VLE using Specifications such as IMS Enterprise. SRS XML Config File VLE User Accounts Scenario 2

  5. Users Web Browser Academic User has added a link to a resource, from a course page in the VLE, for all his students to use. A Student User logs in to the Institutional MLE and follows the screens to the VLE (auto-login to VLE at appropriate position) MLE VLE The URL to the resource is a Search against ANGEL, and includes information about the users group and the resource ID. ANGEL determines where best to get that resource from, for members of THIS group. MLE User DB ANGEL Resource Manager XML Config File Resource Management Scenario 3

  6. Users Web Browser ANGEL transfers Cookie to Browser, and redirects Browser to point at appropriate resource VLE Local & Remote Resources ANGEL Resource Manager LMS Appropriate cookies or certificates are transferred to the users machine and the browser is pointed to the required resource server, without the user having to login again. This uses Specifications such as Shibboleth and PAPI. XML Config File Resource Management Scenario 3 Academic User has added a link to a resource, from a course page in the VLE, for all his students to use. A Student User logs in to the Institutional MLE and follows the screens to the VLE (auto-login to VLE at appropriate position) The URL to the resource is a Search against ANGEL, and includes information about the users group and the resource ID. ANGEL determines where best to get that resource from, for members of THIS group.

  7. Users Web Browser Academic User goes to MLE web site and queries Library Services for resources on engineering. Once a single item is identified, a feature in the MLE allows the academic to associate the resource with a course and ask ANGEL to add it to the VLE resources page. MLE VLE Local & Remote Resources ANGEL takes the Resource ID, the Course ID and the VLE reference and creates a search URL to insert in the VLE page. MLE User DB ANGEL User & Resource Manager LMS XML Config File Resource Discovery Scenario 4 When a student clicks this resource link, they could be presented with a number of options, including purchase information from the University Book Shop or Amazon, or just be presented with the electronic version directly. Scenario 3.

  8. ANGEL can be used by other interface tools (VLE/MLE/ITE/Portals etc) ANGEL can support multiple systems (SRS/LMS/resource services) Used to support a wide range of tasks A number of Scenarios already implemented Many more scenario variations are possible Conclusion

More Related