Develop Single Sign On Solution - Java (SAML)/ OAUTH

Background Education Services (ES) uses a third party COTS system named Canvas LMS ([login to view URL]) that offers online educational training module (training content and tools) to training organisations. Canvas LMS is hosted on AWS. Currently, ES clients (e.g. student, teacher, administrator and organisations) log into the Canvas LMS system using Canvas LMS user interfaces (e.g. Login interface). ES also developed an in-house developed custom web (web java) based reporting application that the company use to report on training modules. The reporting application (‘Lighthouse’) is hosted on the ES infrastructure. These reports are also used by ES clients (e.g. student, teacher). ES clients log into the reporting application by using reporting application’s login interface (e.g. login page). ES clients need to login separately into two different systems (Canvas LMS and Reporting application) to get the services that we offer to our clients. The experience is not seamless and superior given that they have to login separately. ES already uses Canvas LMS to provision/create two accounts; a registered organisation (RTO) account and an RTO administrator account. ES will continue to use this function as it is. High Level concept interactions between SSO solution and Canvas LMS+Lighthouse - Each user account (student, teacher) will be created by calling API/Webservices (to be developed as part of this process) and stored in the ES SSO solution. This API will require the following information: o Username o Password o First Name o Last Name o RTO account ID o Email address o User type (Student, Teacher, Administrator, Regulator) - Once user is created, user should be able to log in to the company COTS Canvas LMS and also the internal ‘Lighthouse’ system using the same credentials utilising SSO (e.g. SAML based). Use Case • Generally, ES directly goes into Canvas LMS admin interface to create RTO accounts and Administrator account. Therefore, an RTO account and Administrator account already exist. This function will stay as it is. • When a student under an RTO wants to register, they fire up SSO registration page and provides registration information (e.g. frame, blame, email, username, password, RTO Id from an already loaded select list that will be same as canvas RTO ids). User clicks register. SSO solution stores the details in its own database and send requests o to Canvas to create the user in Canvas LMS and, o to Lighthouse to create the user in Lighthouse. • User now fires up SSO solution login page, user puts username and password. SSO solution authenticates the user using SSO solution database shows links to access both Canvas and Lighthouse. Depending on which application the user click, the user is validated and is given access to either Canvas LMS and/or Lighthouse. Relevant Technology information • Build an identity provider using SAML • Integrate identity provider with Canvas LMS using SSO (through SAML) o [login to view URL] o [login to view URL] • Integrate identity provider with Lighthouse (configured through SAML) • User management (removal of user, suspension etc.) Further useful links [login to view URL] [login to view URL] High Level requirement We need to do the following - Develop a web based single sign on (SSO) solution that offers single sign on to both Canvas LMS and Lighthouse. - Develop SSO management o Admin login and management o Suspend an account o Remove an account o Update an account o List all users Expected Technology stack You are expected to develop the solution using Java (JEE5+ [JSF2/EJB3] or spring stack of technologies).