Overview
Your Users can sign in to the SoftwareOne Services Portal in two main ways:
-
Using Single Sign On
-
Using any existing Microsoft or Google account (including your workplace account, if your workplace allows that)
-
Using a dedicated connection that limits logins to your workplace identity provider only (aka an ‘Enterprise Federation’)
-
-
Using a username and password, with MFA.
Both methods answer the same question: "Is this person who they say they are?", they differ in who holds your credentials and who checks them.
This article explains how each method works, what the sign-in experience looks like, and the benefits and drawbacks of each, so you can decide which fits your team.
A few terms used throughout:
-
Authentication is the process of proving your identity when you sign in.
-
Single Sign-On (SSO) lets you use one set of credentials, managed elsewhere, to access several applications without creating a separate password for each.
-
Identity provider (IdP) is the service that holds your credentials and confirms your identity, such as Microsoft, Google or your company's directory.
Single Sign-On with Microsoft and Google
With Microsoft and Google SSO, you sign in using an account you already have with that provider, so you do not need to create or remember a separate password for the application.
How it works
-
On the sign-in screen, you choose "Continue with Microsoft" or "Continue with Google".
-
You are taken to the provider's own sign-in page, where you enter your credentials there (or are recognized automatically if you are already signed in).
-
The provider confirms your identity and asks you to approve sharing basic profile details, such as your name and email address, with the application.
-
You are returned to the application, signed in. The application never sees your Microsoft or Google password.
The provider handles all credential checks, including any multi-factor authentication you have set up on that account. Behind the scenes, this relies on open, widely used standards (OpenID Connect, built on OAuth 2.0), which is what makes the handoff secure.
Best suited to
-
Individuals and teams who already use Microsoft 365 or Google Workspace accounts
-
Users who want a fast, one-click sign-in
To use SSO with Microsoft or Google, please check the following article:
Accessing the SoftwareOne Services PortalEnterprise Federation
Enterprise Federation connects the application directly to your organization's own identity provider and limits logins to that IdP for all users with specified email domains.
How it works
-
Your IT administrator sets up a trusted connection between the Sercices Portal and your organization's identity provider (for example, a corporate directory or a service such as Microsoft Entra ID, Okta or Ping Identity). This is done once.
-
When an employee enters their work email address or selects their company, they are redirected to their organization's usual sign-in page.
-
Your identity provider verifies the employee, applying your company's own rules, such as password policy, MFA and device checks.
-
Your identity provider sends back a signed confirmation of who the employee is, and the application signs them in.
The connection typically uses one of two industry standards: SAML 2.0 or OpenID Connect. Your IT team will know which one your identity provider supports.
Best suited to
-
Companies that already manage employees in a central directory
-
Organizations with security, compliance or audit requirements
To setup an Enterprise federation, please send a request to support@softwareone.com to get that work initiated.
Username and password
Username and password sign-in is fully supported and is the simplest method: you create an account directly with the application and prove your identity with credentials only you know.
How it works
-
You register with an email address or username and choose a password.
-
The application stores a protected form of your password (never the password itself) alongside your account.
-
Each time you sign in, you enter your credentials and the application checks them against what it has stored.
-
If they match, you are signed in. If you forget your password, you can reset it through a link sent to your email address.
This method can be strengthened with multi-factor authentication (MFA), which asks for a second proof of identity, such as a code from an authenticator app, in addition to your password.
Best suited to
-
Individuals and small teams with no company-wide login system
-
Users who prefer not to link another account
-
Situations where you need to give access quickly, with no setup on your side
Benefits and drawbacks at a glance
No single method is best for everyone: username and password is the easiest to start with, Microsoft and Google SSO is the quickest for users, and Enterprise Federation gives organizations the most control.
|
|
Username and password |
Microsoft / Google SSO |
Enterprise Federation |
|---|---|---|---|
|
Who holds the credentials |
The application |
Microsoft or Google |
Your organization |
|
Setup effort |
None; users register themselves |
None to low; users choose a provider |
Moderate; needs your IT team to configure once |
|
Main benefits |
Works for anyone with an email address; no dependency on a third party; familiar to everyone |
One click to sign in; no new password to remember; provider's MFA and security apply; fewer password resets |
Central control of access; your own security policies and MFA apply; automatic access removal for leavers; meets many compliance requirements; one work login for all company apps |
|
Main drawbacks |
One more password to remember and protect; passwords can be reused, guessed or phished; password resets add support effort; MFA must be enabled separately |
Relies on the provider being available; users need a Microsoft or Google account; a personal account may be used where a work account is expected; the organization has limited control over those accounts |
Requires IT involvement and technical setup; depends on your identity provider being available; sign-in problems may need your IT team to resolve; may need to be set up per organization |
|
Typical users |
Individuals, small teams, guests |
Small to mid-sized teams on Microsoft 365 or Google Workspace |
Mid-sized and large organizations |
Choosing a method
Choose the method that matches how your team already manages identity, and remember that the methods can be offered side by side, so different people can sign in in different ways.
-
No central login system, or just getting started: use username and password, and turn on MFA.
-
Your team already uses Microsoft or Google accounts: use Microsoft or Google SSO for a fast sign-in with no extra passwords.
-
You need central control, security policies or compliance: use Enterprise Federation with your organization's identity provider.
Whichever method you use, we recommend enabling multi-factor authentication where it is available, since it significantly reduces the risk of unauthorized access.
If you are unsure which option suits your organization, or need help setting up Enterprise Federation, contact our support team and support@softwareone.com