Off-The-Job changes in line with the ESFA Funding Rules 2022/23

Click here to see our planned changes to support the new funding rules. Get involved by upvoting, commenting and following the topic to receive updates!

Scheduled Maintenance: Saturday 8th October 2022 - 07:00-07:30am

On Saturday morning, we're carrying out server maintenance. 

Please ensure you have saved any work and have logged out prior to 7:00am to avoid any potential loss of data.

Help centre

Submit a ticket Log in


We (OneFile) will use yourself as the identity provider to allow your users to authentication, we support SAML2 as a service provider. Our Meta data is available at the following URL:

Provisioning SAML users

We currently only support linking OneFile users to your SAML accounts through API calls to link the account. This was designed to be used with our Webhook integration. In this process, when a user is created or modified, then we send a webhook to you. For user create webhooks you can then call our api to link the new user to the SAML account. 

User flow

  • When configuring your SAML Integration within OneFile, you must provide a domain field. This is used on our login page, if your users arrive at our site directly. Users click SSO on our login page, type in your domain (e.g. and we will use SAML2 Post binding to send the user with an Authnrequest. 
  • We will give you a link such as{guid}. This guid is unique to your integration and you can use this in a simple HTML link on your site to start the authentication process for your users. This will generate and POST the Authnrequest to your system. 


As the Service Provider we will send you an AuthnRequest

  • We only use POST binding.
  • Our Authnrequest is not signed. 

SAML Response

  • We only support POST binding. 
  • We do not process any additional attributes.  
  • We expect the Subject NameId to contain a guid, which we refer to as the SAMLID. This guid is the representation of the user in your IdP system. 
  • We do support unsolicited SAML Response processing, so you can send us a SAML Response directly. 
  • We expect your SAML response to be signed using the certificate provided to us when you configured the integration in our system. 
  • SAML Responses must be signed using SHA256. 
  • RelayState is currently not implemented.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.