Moodle UNI•Login authentication

Setup

• Place the plugin in the folder auth/unilogin
• You need codes and secrets for the webservice and application from UNI•C   

Settings

Applikations & WS ID + secrets

You should get these from UNI•C when registering

Login type

You can log users on in two way - using Single Sign-On (SSO) or Single Log In (SLI). Using SSO users are automatically logged in, if they are already logged into another service with theirUNI•Login. Using SLI they must always enter their credential.

Validation strategy

When a user has authenticated to UNI•Login he is sent back to moodle with a ticket. In addition to checking that the ticket matches the secret from  UNI•C, the ticket can be validated in two ways. 

Either all tickets are saved in the database, to ensure that a ticket is only used once, or a check is made to ensure that the ticket has beeen issued with a certain timeframe (see below).

Validation windows

The maximal age, in seconds that a ticket can have in order for it to be considered as valid. The window should not be shorter than the time it takes to redirect the user's browser.

Login behaviour, text and selector

Login can work in two ways:

• Link will insert a link on moodle regular login page, using javascript
• Redirect will redirect the user as soon as they click login. This means users will only be able to login with uinlogin.

Lock user fields

Allows you to choose if the fields should be updated on creation or on each login, and if users should be allowed to update the fields themselves.