Translations by Hasiotis Nikos

<h3>WWW Root</h3> <p>The web address of the root of the remote application, e.g. http://www.example.com</p>

<h3>Name</h3> <p>A name to identify your system to the remote administrator</p>

<h3>They SSO in</h3> <p>Enable this option to allow users from the remote site to roam to your Mahara site, without having to enter their username and password.</p> <h3>We SSO out</h3> <p>Enable this option to allow your users to roam from Mahara to the remote site, without having to re-sign on there.</p>

<h3>We import content</h3> <p>Not all network-enabled applications support this, but if they do, this will allow users of the remote site to import content here.</p> <p>It depends on 'They SSO in' and it's sensible to also have 'We auto-create users' set as well</p>

<h3>Auto-create users</h3> <p>If a user we have no record of authenticates successfully, we can retrieve his details from the remote server, and create a record for him.</p>

<h3>Update user info on login</h3> <p>Enable this option to bring over user data from the remote site on login, and update your user record with any changes.</p>

<h3>SAML 2.0 field for Surname</h3> <p>Enter the name of the attribute passed by the Identity Provider (IdP) that contains the user's last name</p>

<h3>Port number</h3> <p>The port number that the remote application is listening at. You probably won't need to change this unless you're connecting to a https service, or your remote app is running on a non-standard port.</p>

<h3>Parent Authority</h3> <p>If you set a parent authority, users will be able to log in using that authority as well as via SSO.</p> <p>For example, you could set up LDAP authentication and have that be the parent of this authority. That means that users will be able to log in via Mahara's inbuilt login forms using their LDAP details, as well as via SSO from an external authentication.</p> <p>You do not have to set a parent authority. If you do not, users using this authority will only be able to access Mahara by SSO.</p>

<h3>Hostname or Address</h3> <p>Hostname of the computer that will provide the authentication service. This can also be an IP address, like 192.168.0.1</p>

<h3>Login Error Message</h3> <p>When there is no parent authority, users are only able to log in via SSO and are unable to use Mahara's login form.</p> <p>Enter a message here to show to users who try to log in using Mahara's login form. This message should contain instructions on how a user can gain access to Mahara through SSO.</p>

<h3>Simple SAML PHP Library Path</h3> <p>The fully qualified path to the library directory of Simple SAML PHP. eg: if the fully path to the bootstrap autoload.php is /some_path_to/simplesamlphp_1_3/lib/_autoload.php then this value should be /some_path_to/simplesamlphp_1_3/</p>

<h3>Simple SAML PHP Configuration Path</h3> <p>The fully qualified path to the configuration directory to be used for this Service Provider (SP) Simple SAML PHP. eg: if the fully path to the config.php is /some_path_to/simplesamlphp_1_3/config/config.php then this value should be /some_path_to/simplesamlphp_1_3/config/</p>

<h3>Update User Information on Login</h3> <p>If this is set, then the users firstname, lastname, and email address values will be updated from the Identity Provider (IdP) values passed through.</p>

Sorry, this username is already taken

<h3>Remote user</h3> <p>Match the user attribute value to the remote username field assigned to a given user (not the real Mahara user name). </p>

<h3>Institution Check Value</h3> <p>This is the value that will be checked against the Institution Attribute value, as passed from the Identity Provider (IdP) that shows which institution the user belongs to. If the Institution Regex checkbox is selected, then this value can be a regular expression, that will be used to check against the Institution Attribute value.</p>

<h3>Institution Regex</h3> <p>If this checkbox is checked then the value in the Institution Check Value field will be treated like a regular expression</p>

<h3>Institution Attribute</h3> <p>This is the attribute that will be passed from the Identity Provider (IdP) that shows which institution the user belongs to. These usually directly correlate to LDAP attributes (the signin service of the IdP) eg: eduPersonOrgDN</p>

<h3>SAML 2.0 field for First Name</h3> <p>Enter the name of the attribute passed by the Identity Provider (IdP) that contain's the user's first name.</p>

<h3>SAML 2.0 field for email</h3> <p>Enter the name of the attribute passed by the Identity Provider (IdP) that contains the user's email address</p>

<h3>LDAP version</h3> <p>The version of the LDAP protocol your server is using</p>

<h3>User type</h3> <p>Select how users are stored in LDAP</p>

<h3>User attribute</h3> <p>The attribute used to search for users (often 'cn')</p>

<h3>LDAP field for Surname</h3> <p>Enter the name of the field in the LDAP record that contains the user's last name</p>

<h3>Search subcontexts</h3> <p>Search for user in subcontexts</p>

<h3>LDAP field for First Name</h3> <p>Enter the name of the field in the LDAP record that contain's the user's first name.</p>

<h3>LDAP field for email</h3> <p>Enter the name of the field in the LDAP record that contains the user's email address</p>

<h3>Contexts</h3> <p>List of contexts where users are located. Separate different contexts with ';'. (e.g., 'ou=users,o=org;ou=other,o=org')</p>

<h3>Password</h3> <p>The password for the Distinguished name</p>

Items to show

I agree to the Terms and Conditions

<h3>Start Date</h3> <p>You can enter the date in any format you like, for example '2nd of April 2008' or 'November 2005'.</p>

<h3>Interests</h3> <p>The Interests section allows to list your personal and/or professional interests. This might include your hobbies, sporting activities, volunteer work, areas of research and expertise etc. Listing your Interests will help employers form a better picture of who you are and what you would bring to their organisation.</p>

<h3>Start Date</h3> <p>You can enter the date in any format you like, for example '2nd of April 2008' or 'November 2005'.</p>

<h3>Start Date</h3> <p>You can enter the date in any format you like, for example '2nd of April 2008' or 'November 2005'.</p>

<h3>Start Date</h3> <p>You can enter the date in any format you like, for example '2nd of April 2008' or 'November 2005'.</p>

<h3>Start Date</h3> <p>You can enter the date in any format you like, for example '2nd of April 2008' or 'November 2005'.</p>

If you leave this blank, the name of the field will be used

%sFill out your résumé%s in order to add more fields!

Editing Plan

Edit Plan

Email already activiated

You must agree to the copyright notice

The name field is required

File upload failed: try uploading the file again

Selecting failed: file or folder does not exist any more

Removing failed: file or folder does not exist any more

Moving failed: file or folder does not exist any more

Enforce a site-wide maximum quota