Federated identity and single sign-on
Enable federated access through Cropin’s SSO feature
At Cropin, we have been incorporating several new features on our agritech platform to provide a smooth user experience and increase efficiency. One such aspect is enabling federated access for your workforce through SSO and MFA.
How does this work? Let us say that your organisation uses CRM (customer relationship management) solutions like SAP or Salesforce. Cropin enables integration with their identity providers to facilitate logging into Cropin’s apps using the user’s credentials for the CRM.
Cropin’s out-of-the-box functionality provides for the most usable and friction-free authentication experience. We achieve this with:
- Modern, industry-standard authentication schemes like SAML, Oauth2, OpenID connect
- Third-party identity federation like Google, Facebook, Twitter, LinkedIn, Github, and the like
- Advanced MFA using either a guardian application like Google Authenticator or SMS/email
- Centralised provisioning and de-provisioning of user accounts
- Role-based permissions
- Multi-tenant and cloud-enabled authentication
What are the benefits?
The new SSO feature in Cropin’s applications guarantees a positive impact on productivity. Firstly, it helps users skip the process of inputting log-in credentials each time they need to access a service. Secondly, it also reduces the burden of having to remember multiple, 10 to 18 characters long passwords (alphanumeric, uppercase, and special characters included), and the frustration of having to reset it whenever you forget it. Instead, it establishes a one-point secure entry to all of CropIn’s apps at a click of a button and prevents security breaches caused by compromised credentials.
SSO makes it easier for organisations to enforce information security policies. Organisations can link and administer Cropin application access through access and roles defined centrally in the organisation. For instance, when an employee leaves or changes departments, separate user management (enabling/disabling access) within Cropin applications is not required. It also improves cost-efficiency by eliminating the costs associated with password reset and downtimes.