Difference between revisions of "R27 Patch: 16th September 2017"
(Created page with "This page details the content that has been released in the patch named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release...") |
|||
Line 1: | Line 1: | ||
This page details the content that has been released in the patch named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release, please take a look at the [[Version History]] page to see all Sprints and Releases. | This page details the content that has been released in the patch named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release, please take a look at the [[Version History]] page to see all Sprints and Releases. | ||
− | == | + | == ZD8599 == |
− | + | ===SSO Patch=== | |
− | === | + | Due to an issue with the way an institution was passing across the eduPersonPrincipalName value in SSO we had to update the way that we were parsing this. Previously UnionCloud took the 'Alias' part of an email address, i.e. the bit before the @ symbol, and compared it to a set of identifiers within the Student Table, however a new SSO Union are allowing duplicate alias' for their users because they differentiate them by using an identifier after the @ in an email address. |
− | |||
− | |||
− | + | For example, most unions with users of same initial and name, let's say C. Smith would be listed in the following way; | |
− | + | c.smith@institution.ac.uk | |
− | + | c.smith1@institution.ac.uk | |
− | + | c.smith2@institution.ac.uk | |
− | |||
− | + | However they were using the following method, based on the year a users course originated. | |
− | + | c.smith@2016.institution.ac.uk | |
− | + | c.smith@2017.institution.ac.uk | |
+ | c.smith1@2017.institution.ac.uk | ||
− | + | After reviewing how we parse these email addresses we have updated the UnionCloud Single Sign on process to clarify the entire email address now, rather than just the 'username' portion. | |
*This issue has been resolved. | *This issue has been resolved. | ||
− | == | + | == ZD8569 == |
[[File:relevant_image.png|thumb|description]] | [[File:relevant_image.png|thumb|description]] | ||
===Title=== | ===Title=== | ||
− | |||
Details | Details | ||
*This issue has been resolved. | *This issue has been resolved. | ||
+ | |||
== Uncat == | == Uncat == | ||
=== Minor uncategorised fix === | === Minor uncategorised fix === | ||
− | + | N/A | |
− | |||
− |
Revision as of 14:48, 20 October 2017
This page details the content that has been released in the patch named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release, please take a look at the Version History page to see all Sprints and Releases.
ZD8599
SSO Patch
Due to an issue with the way an institution was passing across the eduPersonPrincipalName value in SSO we had to update the way that we were parsing this. Previously UnionCloud took the 'Alias' part of an email address, i.e. the bit before the @ symbol, and compared it to a set of identifiers within the Student Table, however a new SSO Union are allowing duplicate alias' for their users because they differentiate them by using an identifier after the @ in an email address.
For example, most unions with users of same initial and name, let's say C. Smith would be listed in the following way;
c.smith@institution.ac.uk c.smith1@institution.ac.uk c.smith2@institution.ac.uk
However they were using the following method, based on the year a users course originated.
c.smith@2016.institution.ac.uk c.smith@2017.institution.ac.uk c.smith1@2017.institution.ac.uk
After reviewing how we parse these email addresses we have updated the UnionCloud Single Sign on process to clarify the entire email address now, rather than just the 'username' portion.
- This issue has been resolved.
ZD8569
Title
Details
- This issue has been resolved.
Uncat
Minor uncategorised fix
N/A