Not only do we provide extensive integration via API’s and CSV with front and back office systems, we also offer integration with other 3rd parties such as mobile app providers, agency websites, managed service systems and agency client time and attendance systems.
...
- Your application requests an access token from the RSM InTime web services
authenticate(java.lang.String agencyRefCode, java.lang.String username, java.lang.String password) - Your application requests a login token for a particular user
getSingleSignOnToken(java.lang.String token, java.lang.String username, int timeToLiveSeconds) - Your application creates a URL to your RSM InTime site. The token retrieve in stage 2 is placed on the URL
https://timesheets.yoursite.com?ticket=xxxxxxxxxxxxxx
...
IMPORTANT NOTE ON SECURITY: when single sign on capability is enabled for your site the password expiry for user accounts has to be disabled in RSM InTime. You are delegating authentication authority to your external system and must be aware of and take account of the security implications of this.
Ability to choose single sign on users
You can now choose which users are required to use single sign on. Within security settings we have provided tick boxes that allow you to choose if groups of users must use single sign on. If not ticked users can use their username and password or single sign on. If ticked the users will only be able to use SSO.
You will also be able to apply mandatory SSO log in for individual users as well. Go to the user's profile and on the main tab you will see a requires SSO tick box. For all other users, the requires SSO tick box is at the bottom on the main tab page.
Please note: managers and providers cannot use OpenId/Okta/Azure SSO, but they can use web services SSO.
Batch Placement upload
As an admin user it is possible to bulk upload placements via a CSV file which conforms to our standard RSM InTime import format.
...