JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH Archives

JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH  July 2017

JISC-SHIBBOLETH July 2017

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Liberate and attributes

From:

"Andy Swiffin (Staff)" <[log in to unmask]>

Reply-To:

Discussion list for Shibboleth developments <[log in to unmask]>

Date:

Wed, 5 Jul 2017 09:17:19 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Hi,



I hadn't seen a reply to this, there are some important questions that need answering before we could consider Liberate as a possible service.

Particularly, how will it  generate ePe values which are multivalued.   Would a site need to create a multivalued string attribute? Can you consume that?



Regards

Andy







-----Original Message-----

From: Andy Swiffin (Staff)

Sent: 03 July 2017 08:33

To: 'Rhys Smith' <[log in to unmask]>; Discussion list for Shibboleth developments <[log in to unmask]>

Cc: Jisc Liberate Service <[log in to unmask]>; Joe Steele <[log in to unmask]>

Subject: RE: [JISC-SHIBBOLETH] Liberate and attributes



ePSA : we could get around by turning it into a group or just combining the values with FIM so not an issue.



ePe:  So, how do you propose supplying Liberate for anyone running Tallis Aspire?    We could combine all of the values,  using FIM,  into one multivalued string attribute, can you consume that and release it as ePe?  This would be a complete show stopper for anyone using Tallis.



Ambidextrousness concerning cn or upn to login?  Very very easy.

In resolver:

            <![CDATA[

                (|(userPrincipalName=$requestContext.principalName) (cn=$requestContext.principalName))

            ]]>



In login.config:        userFilter="(|(userprincipalname={0})(cn={0}))"



Not an issue for us as we'd just mandate upn for everything and ditch cn, it fits in with O365 and so users now expect it.   You can just use upn?





So,  the bottom line is how you can consume the multivalued ePe,  provided you can consume a multivalued string we'd just create an ADLDS attribute and do the work to populate it here.



We would like to make this work,  Our focus is turning to Azure AD for authentication wherever possible and the attraction of getting Shibboleth, if we still need it,  off-premise is very attractive



Andy





-----Original Message-----

From: Rhys Smith [mailto:[log in to unmask]]

Sent: 30 June 2017 16:17

To: Discussion list for Shibboleth developments <[log in to unmask]>; Andy Swiffin (Staff) <[log in to unmask]>

Cc: Jisc Liberate Service <[log in to unmask]>; Joe Steele <[log in to unmask]>

Subject: Re: [JISC-SHIBBOLETH] Liberate and attributes



Thanks for the questions Andy, I’ve responded inline below.



One thing to note is that the Liberate service we’re launching later this year is meant to be just a starting point - with just enough features to work for those with simple requirements initially; it’ll be developed to be much more fully featured over the following months/years based off of customer feedback and its applicability and flexibility should widen considerably. It’s definitely not going to be released as-is and then not move forward.



So with that in mind, some answers:







> Liberate needs to generate the 3 main attributes ePSA, ePTID and ePe

> (obviously)

>

> ePSA:  We currently use scripts in resolver to generate the Staff/Student/Member based on an ldap attribute.

> For example, to generate the student value we do:

>

> if

> ((dUNUNIaccountTypeValue=="UG")||(dUNUNIaccountTypeValue=="PG-Taught")

> ||(dUNUNIaccountTypeValue=="PG-Research"))

> {

>                 if ((status=="C")||(status=="P1")||(status=="XB")||(status=="PE")||(status=="CO")||(status=="X")||(status=="CT"))

>                 {

>                                 eduPersonAffiliation.getValues().add("student");

>                                 eduPersonAffiliation.getValues().add("member");

>                 }

> }



Initially, we don’t support scripted attributes (for security reasons). We do support mappings (incl. regex) however, so if the above was based off a a single attribute, that would work fine, so e.g. you’d configure the ePSA attribute to connect to dUNUNIaccountTypeValue and have a set of mappings:



UG -> member

UG -> student

PG-Taught -> member

PG-Taught -> student

etc



That’s all easy to do in our web management UI.



In your particular case though, looks like you’re combining information from two separate attributes - “dUNUNIaccountTypeValue" and “status”? At the service launch, we wouldn’t be able to support that but I suspect you’re not the only one doing similar things so suspect it’ll just be a matter of time before we do.







> ePTID:  Will liberate be able to retain our existing values so that users don’t lose their customisation?



Yes (unless you’ve done something weird). When we instantiate your Shib IdP, we give it a default entityId and create a salt, but these can be overridden in the management UI. So assuming that when you move to the Liberate hosted IdP we give it the same entityId as your old production IdP, the same salt, and connect it to the same source attribute from your directory, all of the generated values should be identical.









> ePe:  This is the complicated one.   Mostly it’s just a single value so easy enough.  But what about Tallis reading lists.  This is a multivalued ePe, one single line string for the students and multivalues for each staff readinglist.   Currently we store both in separate string attributes.    For the staff one, we have a string attribute which is semicolon separated values.   The IdP then tokenises that in a resolver script and pushes values into ePe viz:

>

>       if (requestContext.getPeerEntityId()==("https://login.talisaspire.com/entity"))

>       {

>                if  ((typeof dUNUNItalisePeStaff != "undefined") && (dUNUNItalisePeStaff.getValues().size()>0))

>                {

>                          stafftalisepe=dUNUNItalisePeStaff.getValues().get(0);

>                         talisentitlement=stafftalisepe.split(";");

>                         for (values = 0; values < talisentitlement.length; values++)

>                         {

>                                    eduPersonEntitlement.getValues().add(talisentitlement[values]);

>                          }

>               }

>               if  ((typeof dUNUNItalisePeStudent != "undefined") && (dUNUNItalisePeStudent.getValues().size()>0))

>               {

>                         studenttalisepe=dUNUNItalisePeStudent.getValues().get(0);

>                         eduPersonEntitlement.getValues().add(studenttalisepe);

>                 }

>       }

>

> Can liberate do this?   Or what else would we have to do to be able to do this?



Not at the moment, no, that’s a fairly complex requirement. I suspect that Liberate will have to support scripted attributes in some form at some point, it just won’t at the start.







> We authenticate users who enter either cn or upn in the login box, can liberate do this?  (we found many users entering upn as they do for O365 after we migrated to Azure).  If only one of them, we would want to use only upn for authentication now.



Not to begin with no - out of interest, how do you actually achieve this in the Shib IdP today? I don’t think I’ve ever seen that set up, would be interested in what the config looks like.









> BTW, we aren’t authenticating or providing attributes from AD (which we keep very clean of unnecessary data) but from an ADLDS instance (actually a pair) which has userproxyfull objects (not user, so it can do proxy authentication to AD) can Liberate do this?



If it’s LDAP compliant (i.e. if it accepts bind requests and can return LDAP responses incl. the necessary attributes and values) , then it should be able to connect to it. Haven’t tested that one personally yet, but I’d be surprised if there were an issue.





>  I think I heard it said in the webinar that you can also take any other LDAP attribute (givename, sn, employeeID) and punt those out in an assertion, we’re probably going to move the things that need this kind of thing somewhere else, but just in case, can you confirm this?



Yep, should be able to deal with any LDAP attribute. Users of the management UI can choose from a predefined (by us) list, but if you want new attributes adding, we can easily do that. You also configure the attribute release stuff on the same pages in the UI.



Rhys.

--

Dr Rhys Smith

Chief Technical Architect, Trust & Identity Jisc



T: +44 (0) 1235 822145

M: +44 (0) 7968 087821

Skype: rhys-smith

GPG: 0x4638C985

Lumen House, Library Avenue, Harwell Oxford, Didcot, OX11 0SG



jisc.ac.uk



Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.





The University of Dundee is a registered Scottish Charity, No: SC015096

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
April 2015
March 2015
February 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager