[log in to unmask]" type="cite">Perhaps it was as clear as mud. The majority of users have to click on the Athens button in order to login with their institutional username and password. Changing the UK Federation button to "Login via your institution ID" will be just as confusing, if not more so, at this time. We'd have to tell users to ignore the button that says "Login with your institutional ID", click on the Athens button instead, and then login with your institutional ID! But I do agree, the phrase UK Federation is meaningless to users. SueJane CHARLTON <[log in to unmask]> 04/07/2007 12:29:27 >>>I agree we're a bit stuck with the 3 login buttons for the moment, but maybe we could at least change the one that says "Login via UK Federation" to "Login via your institutional ID" or "Login via your institutional username and password" Jane ________________________________ From: Discussion list for Shibboleth developments on behalf of Sue Stevens Sent: Wed 04/07/2007 12:11 To: [log in to unmask] Subject: Re: Federation gateways - using TRLs Oh, yes I agree. But unfortunately it's not as simple as that. For example, EDINA resources list three login buttons, which are currently labelled: Login via Athens Login via direct access Login via UK Federation Now, all these buttons work for our users. But, you could use your institutional username and password to login via both the Athens and the UK Federation routes, depending on whether your institution is using AthensDa, the Shibb to Athens Gateway or the UK Federation. So changing the UK Federation button to institutional username would work for those resources that are live on the Federation. But it would be a problem for an institution using AthensDA or the Shibb to Athens Gateway for resources not on the Federation because you still need to use the Athens button, but with an institutional username. And at the moment, that still means the majority of resources. Clear? As mud... The Shibb stuff is great, our users love it. But explaining what they have to do to get logged in sure was easier when all we had was a classic Athens login box and every institution used the same! If anyone has some neat presentation idea, we'd be glad to hear it! SueJane CHARLTON <[log in to unmask]> 04/07/2007 11:41:35 >>>Sorry! this is a sidetrack from the issue about using TRLs - I think it would be more straighforward for the user if the login page simply said "please log-in using your institutional username and password" instead of "login via UK Federation" as most of them won't know what this is and it will confuse them. ------------------------------------ Jane Charlton Access Management Outreach Co-ordinator, JISC <mailto:[log in to unmask]> * [log in to unmask] <mailto:[log in to unmask]> ( +44 (0)117 3310672 M: +44 (0)776 017 3223 F: +44 (0)117 954 5078 : www.jisc.ac.uk ________________________________ From: Discussion list for Shibboleth developments on behalf of Alistair Young Sent: Wed 04/07/2007 09:59 To: [log in to unmask] Subject: Re: Federation gateways - using TRLs This is the hot topic here too. Just wondering what the chances are of these appearing in the uk federation as SPs in their own right? We're not sure what way to go just now. Our users are seeing more and more "login via uk federation" links alongside "alternative login" links (gateway). Do you think these journal level articles will be available as resources in the federation? Or will they more likely be behind something like SS, which could then act as an SP in the fed? Alistair -------------- mov eax,1 mov ebx,0 int 80h On 4 Jul 2007, at 09:28, Sue Stevens wrote: Hi Masha, We're grappling with exactly the same questions here at Cardiff and are using TRLs. Our discoveries so far indicate that you can do journal level linking via the Gateway so long as the DSP supports it. The down side to that of course is having to find what the syntax should be and then test it with all your DSPs. We have only just started looking at this, but I can tell you Ovid support is as I've been testing it with them. Here's an example of the syntax for the Journal of Cell Biology on Ovid via our IdP and the Federation gateway: https://idp.cardiff.ac.uk/shibboleth-idp/SSO?providerId=https%3A%2F%2Fsh ibboleth.ovid.com%2Fentity&shire=https%3A%2F%2Fshibboleth.ovid.com%2FShi bboleth.sso%2FSAML%2FPOST&target=https%3A%2F%2Fshibboleth.ovid.com%2Fsec ure%3FT%3DJS%26NEWS%3DN%26PAGE%3Dtoc%26SEARCH%3D00004639%2D000000000%2D0 0000%2Ekc%26LINKTYPE%3DasBody%26LINKPOS%3D1%26D%3Dovft You can do the same type of linking with Ovid via the Shibb Athens gateway too: http://auth.athensams.net/?ath_dspid=ATHENS&ath_action=shaauth&id=https: //idp.cardiff.ac.uk/shibboleth&ath_returl=http://auth.athensams.net/trl/ 1.0/-/OVID_ONLINE%3FT%3DJS%26NEWS%3DN%26PAGE%3Dtoc%26SEARCH%3D00004639-0 00000000-00000.kc%26LINKTYPE%3DasBody%26LINKPOS%3D1%26D%3Dovft If you're familiar with Ovid at all you'll see it's the same "jumpstart" syntax they use for a classic Athens login, but with the Shibb gateway stuff on the front. For completeness here's the classic Athens version of the above: http://gateway.ovid.com/athens/ovidweb.cgi?T=JS&NEWS=N&PAGE=toc&SEARCH=00004639-000000000-00000.kc&LINKTYPE=asBody&LINKPOS=1&D=ovft Sorry I've only got examples for this one DSP so far. Another 100 and something to go... We also use Serials Solutions, but haven't worked out what we're going to do about that yet. Ditto, walk-in users. Would be happy to share more with you, and vice-versa, when we have it. Regards, Sue Sue Stevens Head of Library Systems Information Services Cardiff University 39-41 Park Place Cardiff CF10 3BB United Kingdom Tel: +44(0)29 2087 4706 Fax: +44(0)29 2087 4285 Email: [log in to unmask] Masha Garibyan <[log in to unmask]> 03/07/2007 20:59:22 >>> Dear all, I wonder if those of you who are already using the Federation gateways to provide Shib access to e-resources, would mind sharing your experiences with the London School of Economics. LSE was one of the first institutions to start testing the Gateways. When we started testing our Gateway-compliant resources, it appeared that a persistent cookie was set when a user accessed a Gateway resource, so that if the user then went to access a non-gateway compliant resource, he would still be directed to the Gateway WAYF, not Classic Athens. Because some key LSE resources were non-gateway compliant (e.g. Westlaw), that wasn't an option for us. Eventually Eduserv suggested using TRLs (their persistent URLs) to overcome the problem. There are two types of TRLs that can be used - one for gateway compliant resources (sets a single session cookie) and one for non-compliant (doesn't set the cookie). This solved the 'cookie' issue but created a new one in that TRLs can only be used for top-level URLs (eg a database homepage), and not individual journals, and LSE provides access to both. My questions are: 1) Have you used/ are you using TRLs? 2) If you have to provide Gateway access at journal title level, how do you do that (LSE uses Serials Solutions to provide access to individual journals, so any examples of Gateway use with SS would be particularly welcome!) 3) If you provide access for walk-in users, how do you display resource links for users (ie separate them from the 'shib'/gateway links). Many thanks in advance, Masha Garibyan LSE Library Projects Team ---------------------------------------------------------------------- Anything in this message which does not clearly relate to the official work of the sender's organisation shall be understood as neither given nor endorsed by that organisation. ---------------------------------------------------------------------- ---------------------------------------------------------------------- Anything in this message which does not clearly relate to the official work of the sender's organisation shall be understood as neither given nor endorsed by that organisation. ----------------------------------------------------------------------
-- Nicole Harris Senior Services Transition Manager JISC Executive Brettenham House (South Entrance) 5, Lancaster Place London WC2E 7EN Tel: 02030066035 Mob: 07734058308
----------------------------------------------------------------------
Anything in this message which does not clearly relate to the official
work of the sender's organisation shall be understood as neither given
nor endorsed by that organisation.
----------------------------------------------------------------------