SSO: Difference between revisions
Jump to navigation
Jump to search
m Added picture |
No edit summary |
||
Line 1: | Line 1: | ||
[[File:Single-Sign-On-SSO-DK.png|thumb]] | [[File:Single-Sign-On-SSO-DK.png|thumb]] | ||
Our Single Sign-on (SSO) module is designed for schools that would like to make it easy for employees and students to use the school's various electronic systems. With the SSO module, users get one login and password that logs them into all the associated services at once. | |||
For example, students can Access the school's LMS system, library system, digital dictionaries and databases with scientific publications - all by signing in with SSO once and for all. | |||
This saves time and effort whenever users need to use one of the school's systems. At the same time, it gives users a simpler everyday life because they do not have to worry about having to keep in mind several logins. | |||
== Prerequisite and purpose == | == Prerequisite and purpose == |
Revision as of 08:38, 28 July 2017
Our Single Sign-on (SSO) module is designed for schools that would like to make it easy for employees and students to use the school's various electronic systems. With the SSO module, users get one login and password that logs them into all the associated services at once.
For example, students can Access the school's LMS system, library system, digital dictionaries and databases with scientific publications - all by signing in with SSO once and for all.
This saves time and effort whenever users need to use one of the school's systems. At the same time, it gives users a simpler everyday life because they do not have to worry about having to keep in mind several logins.
Prerequisite and purpose
Prerequisite
This requires that:
- An installed Active Directory federation services (AD FS) server.
- Access to configuration snap in. Either via Remote PowerShell or directly on the server.
- An UMS installation, licensed to SSO from inLogic.
- A star or new certificate for the address that the AD FS server needs.