1) Athens : BCU staff get checked against the business directory of iCity (Single sign On) SSOwhen they logon. BCU students, as well as being on iCity, have to have an active student record on SITS.
Athens is currently used eg for MyiLibrary ebooks and other resources such as MINTEL where personalisation is needed. The student logs on https://auth.athensams.net first then is directed back to BCU/iCity to check their status. This 'Continue to login' screen (see image left) will lead them back to BCU/iCity to logon, and is triggered by a cookie being installed on their PC.
The student will often need showing how to login via the red tile & 'Find Resources' page which sets this cookie - so taking them though the iCity route verifies them as a student and sets the cookie on their PC). Once logged into iCity, students shouldn't have to log in again to access an Athens resource. Without the cookie on their PC, they will have to know how to find 'alternative login' in order to reach the right Athens login screen as hosted by the provider.
2) Shibboleth via Athens gateway :BCU staff/student logon to Athens https://auth.athensams.net the same as described above, with the same screen but with an extra redirect :'please wait while we transfer' screen :
3) EZproxy : The majority of ejournals and databases via the AtoZ of Resources and via Summon use EZProxy.
In the same way as with Athens, BCU staff get checked via business directory (SSO) of iCity; BCU students also have to have an active student record on SITS. However, logging onto iCity doesn't automatically mean that the student is logged on to EZProxy like Athens.
The EZProxy login looks very similar to that of iCity (see image left) - and any login to a resource via this route will have ezproxy.bcu.ac.uk/ in the address bar at the top. Summon also has a option to login to EZproxy that says "Off Campus? Log in to access full text and more"
4) Digital Library : BCU staff and students are checked via details on Alto record.
5) IP address : Login is checked as coming from a machine/device on BCU network.
6) Username and password (individual logins) : small number of these listed on Username and Password page. (Athens-protected). They are not individual to the user.
7) Publisher passwords from our subscribed resources: set up by the user and used for personalisation, saving search results or bookmarks. Also used by Myilibrary and EBSCOhost when downloading ebooks.
8) Ebook downloads needing password with Adobe Digital Editions - in addition to 7.
9.)Publisher secondary check logins eg MINTEL logon with BCU details first then sends email to student's email to verify.