Version 2.4 Release Note

Transcription

1 Version 2.4 Release Note v2.4 Release Note

2 Welcome to v2.4 of RM Unify As well as implementing several bug fixes, in v2.4 of RM Unify we have introduced two new features which we would like to share with you. The first feature provides an additional way for schools to integrate RM Unify apps which they already use onto their Launch Pads. There were previously two ways to do this, and the integration type depended entirely on the third party app. We re delighted that this new feature increases the total number of apps which can be accessed via RM Unify, even if schools are already using those apps. This feature is only available to RM Unify Premium customers. The second feature is to do with improved login security for RM Unify; we have introduced an Account Lockout Policy to minimise the potential for account hacking by setting a limit for invalid username and password entries. This feature benefits all RM Unify subscription types. This Release Note will fill you in on the two changes associated with this release, linked to a complementary blog available for viewing in the usual place: Release Headlines 1. Cached credentials user matching for RM Unify single-sign on apps that schools are using outside of RM Unify Page 3 to 6 Positively impacts schools that are using an RM Unify single-sign on app outside of RM Unify, but previously could not install the app for free and match their users across. 2. Introduction of an Account Lockout Policy for RM Unify Page 7 to 8 Improves user account security by implementing a new Lockout Policy when incorrect password limits are breached RM Education 2014 Page 2 of 8

3 1. Cached credential user matching for RM Unify single sign-on apps that schools are using outside of RM Unify There were previously two ways that RM Unify Premium schools could integrate subscriptions they already have outside of RM Unify, into RM Unify. This was made possible via: Full matching of user accounts through a brownfield process for apps such as Office 365, Google Apps for Education and I am Learning, and through caching of user credentials, where user accounts are linked up using RM Unify saved password apps. Before taking you through this new method of app integration, let s remind you of the two existing ways you can integrate your online applications into RM Unify: 1. User account brownfield matching for full single sign-on with RM Unify When an app in RM Unify supports full user account matching and integration, you will be presented with a purchasing option to add a free connector to match-up your existing licence and users with RM Unify. Fig 1.1: User brownfield matching allows you to install an RM Unify connector licence to integrate an existing subscription for an app into RM Unify. After working through the user matching wizard and installing the app onto a Launch Pad(s), your users will be able to seamlessly access their account within that app using their RM Unify username and password. 2. Saved password apps Saved password apps allow users to access services which are not available as a single-sign on app in RM Unify. Current examples include Edmodo, Prezi and CC4 Anywhere. Saved password apps can be installed via the App Library and added to Launch Pads. Then, when users click on the tile for that app, they will be prompted to enter their username and password once. When this is done, their credentials are saved into RM Unify, providing single sign-on access to that app from their Launch Pad thereafter. There are currently over 15 saved password apps in the RM Unify App Library for you to install free of charge. RM Education 2014 Page 3 of 8

4 Fig 1.2: Saved password apps allow users to enter their credentials for a specific app once, and then they are stored safely within RM Unify, providing single-sign on thereafter. New to RM Unify v2.4: Cached credential user matching for RM Unify single-sign on apps that schools are already using outside of RM Unify This type of app integration is the third way in which a school can match-up user accounts with RM Unify in order to provide single-sign on access. Before the release of this feature, there were a number of apps which did not support the two existing integration methods i.e. they were not saved password apps and they did not support full brownfield user matching. This new feature relates closely to the functionality already being delivered through saved password apps whereby usernames and password are entered once and then stored securely, but now this is applicable for apps which are available to purchase in RM Unify with single-sign on. How to install an app using cached credential user matching 1. Locate the app in the RM Unify App Library 2. Where the app supports the cached credential feature, you will be presented with an additional licence option on the app information page. The option reads Yes, I already have a licence for the app (and want to use it). If you do already have a licence for this app, select this option, then click Next *. *Note the information displayed in the yellow box at this stage, informing you that automatic user matching will not take place. Users will have to enter their username and password once, when the app is displayed on their Launch Pad. RM Education 2014 Page 4 of 8

5 Fig 1.3: A new option will be presented to you when installing an app which supports the cached credentials user matching feature 3. Read the information displayed. This is an important notice related to the way in which usernames and passwords are stored in RM Unify for the app. Check the box to indicate that you understand, and click Next Fig 1.4: Information must be read, and you must indicate that you understand how the integration works, before you click Next 4. If the app has a unique URL which you usually use to access it, enter that URL in the field. If the app login page is a generic one (for all schools), should also enter that URL into the field. RM Education 2014 Page 5 of 8

6 Fig 1.5: Enter the URL for the app login page in the empty field. 5. Install the app via the existing method of selecting the User Groups and Launch Pads you wish to present it to. 6. Once the app has been added to a Launch Pad, users will be prompted to enter their existing username and password for the app (as displayed in Fig1.2 on page 7). Their credentials will be stored, thus providing single sign-on to that app via RM Unify thereafter. To keep up to date with new apps that are introduced to RM Unify, including those which can be integrated using existing licences outside of RM Unify, check out the RM Unify Trello. We have tagged each app with the type of integration method used to add it to RM Unify. We regularly tweet and update the Trello Board each time a new app is added. RM Education 2014 Page 6 of 8

7 2. Introduction of an account lockout policy for RM Unify Previously, it has been possible for users to submit an unlimited amount of incorrect password entries on the RM Unify login page. Though this has never posed a direct threat to user account security, we have tightened this feature to minimise the impact of user account hacking, should a persistent threat be posed where someone enters a large number of passwords in an attempt to enter an account. The lockout policy which we have introduced in this release sets a limit for the number of incorrect password entries a user will be able to reach before they are temporarily locked out of RM Unify on the device they are using. Let s run through what happens now when an incorrect password is entered. 1. User enters an incorrect username and password combination once. As previously, the user is presented with an error message which tells them that the combination that they have entered is invalid, as shown to the right. 2. Now, users will be presented with this error message just four times, so only four invalid entries can be made. 3. When a user enters a fifth invalid entry, they will be presented with a different error message (shown below), because they have exceeded the set limit. 4. The user is now locked out of RM Unify on the device that they have tried to access it on. The error message will state the IP address for the device. 5. Users can either wait until their account is automatically unlocked, or contact their network administrator to reset their password for them. If your school is using AD Sync as a means of user provisioning for RM Unify, then the password must be reset in the AD. If your school uses a CSV upload, a new username and password must be set in a CSV file, and re-uploaded. RM Education 2014 Page 7 of 8

8 Accounts are locked for 1 minute when the limit is reached before they are automatically unlocked. For every incorrect entry which is made after the fifth entry (within a 24 hour window), the time period will double until it reaches 1 hour, e.g. 1 minute, 2 minutes, 4 minutes, 8 minutes, 16 minutes, 32 minutes, 1 hour. For the latest information on the newest improvements to RM Unify and the addition of new apps, follow RM Unify on or visit the Trello Board. RM Education 2014 Page 8 of 8