Child pages
  • UniDesk System Requirements - Interface
Skip to end of metadata
Go to start of metadata

Self Service

There are no specific requirements for access to UniDesk Self Service. Self Service should work with any modern browser. It requires cookies to be enabled for authentication.

Operator Interface

The Operator view of UniDesk is more complex, it requires:

  • Cookies enabled
  • Javascript enabled

and the use of a supported browser.

Supported Browsers

BrowserVersion
FirefoxFirefox is a supported cross-platform browser. Although officially tested from version 26, recent earlier versions are expected to work without issue. Firefox 4 and below are unsupported, and not expected to work
ChromeChrome is a supported cross-platform browser. Although officially tested from version 32.0.1700, recent earlier versions are expected to work without issue
Internet ExplorerInternet Explorer is a Windows browser, fully supported at versions 8, 9, and 10. Version 11 is partially supported, but is expected to work without significant issues. Version 7 is no longer supported, and not expected to work
OthersOther browsers can be used at the discretion of the Operator, but we are unable to provide additional support. Microsoft Edge is not a supported browser

UniDesk System Requirements - Service Operation


These are the key technical requirements that are essential for the operation of the UniDesk Service:

  • UniDesk is available as a web based service with single sign on. Access to the software for the majority of our members is facilitated via Shibboleth, with federated authentication at each site. Each institution’s service is registered as a service provider with the UK Federation and makes use of the already-existing shibboleth identity providers at each institution.    The version of Shibboleth must be SAML 2 compatible as UniDesk only supports this version.   Members are required to confirm their identity provider and release EPPN (Edu Person Principal Name) as part of configuring SSO

  • The UniDesk service relies on email to communicate with users and operators and UniDesk needs to originate mail on behalf of a UniDesk member institution and have it work exactly as if it had originated from within that institution. We require to route UniDesk mail sent on behalf of a member institution directly into that institution's mail infrastructure. To enable this we setup an Email Trust Relationship between University of Edinburgh and the member. 

    Members are required to:
     
      • Provide us with an endpoint which will accept direct SMTP connections from the University of Edinburgh back end systems
      • Configure their edge firewall to allow our back-end systems to make connections to their designated endpoint(s) and configure the mail system at those endpoint(s) to accept mail from our back-end systems and route it as if it were internally generated

  • Members are required to prepare a location that University of Edinburgh can access to pick up their data for import into UniDesk.  Person data is created from the members golden copy (e.g. HR, Student Feed, AD).   The data is then securely transferred to Edinburgh and scripts automatically schedule the import into UniDesk.  This is typically a nightly process




  • No labels