...
...
...
...
...
...
Use this page to configure Single Sign On This guide walks you through how to assign single sign on (SSO) for the Client Portal by entering the company's authentication details.The following authentication methods are supported:a client and enter their authentication details. This works in the same way as SSO for the payslip portal.
If clients are asking what information they need, they can access Single sign on - a client guide
What information does RSM need?
What authentication methods are supported?
What information does RSM need? Anchor What information does RSM need? What information does RSM need?
| What information does RSM need? | |
| What information does RSM need? |
The OpenID Connect Configuration URL
The Client ID (This may show as Application ID in your identity provider)
The Client Secret
Optionally, your public key
What authentication methods are supported?Anchor What authentication methods are supported? What authentication methods are supported?
| What authentication methods are supported? | |
| What authentication methods are supported? |
OAuth 2.0
OpenID Connect
Contents
| Table of Contents | ||
|---|---|---|
|
Usage
SSO removes the need for users to use a password. Once setup and enabled, the user can login using their company account.
Metadata
An SSO provider may expose some of their configuration.
Enter the Metadata URL and click Populate Details to populate the screen with all details made available. If any details are missing, populate the missing details and click Populate Details again to use the missing values to fill in the Authorization Endpoint.
The Populate Certificate button will only populate the certificate (if available). This is useful for OAuth 2.0 providers.
Options
...
How to set it upAnchor How to set it up How to set it up
| How to set it up | |
| How to set it up |
Go to admin in the top menu heading and select client SSO, then in the client field find the client.
Metadata
You will need to enter OpenID connect configuration URL
Options
Enable SSO - Once this is checked, all client portal users with a matching Email Suffix 1 or 2 email suffix will be able to login by SSO. If this is checked (even if other details are left blank) employees will have a payslip portal user created on commit where they have an email and it's not currently in use as a payslip portal username. The username will be their email address.
Validate Audience issuer -This may be checked if the company wishes wished to validate the audienceissuer. They will need to configure their authentication to provide an audience issuer matching the Payslip Portal URL
Validate Issuer This may be checked if the company wished to validate the issuer. They will need to configure their authentication to provide an issuer matching the Issuer
Validation
Issuer If Validate Issuer issuer.
Validation
If the validate issuer is checked, the returned issuer must match this value.
Claims
...
The payslip client portal supports two claims. If none are entered or available, the default identity name will attempt to be matched to the users Payslip Portal Emailthe user's client portal email address. Check the log after a failed attempted SSO login to see available claims.
Email Claim claim - The name of the claim that will contain the users Payslip Portal Email. client portal email address. For most setups, this will be email
Unique Id Claim claim -The name of the claim that will contain a unique identifier for the user. This may also contain the users email or a unique id for the user. It will be used to verify the user in addition to the email after the first login. For most setups, this will be email
Identification
Client Id id - This allows the company's authentication provider to identify the Payslip Portal client portal and use the correct configuration.
Email Suffix suffix - Users matching one of the provided suffixes suffix will login by SSO. This allows left users or users without a company account to login with a password.
Security
Certificate Certificate - The public certificate used to validated validate the returned token if if Validate Audience or Validate Issuer are checked. Not required for OpenID Connect.Payslip Portal URL This will be pre populated based on the address used to login to InPay. It's used to populate the Authorization Endpoint and to match the sent audience if Validate Audience is checked.
Log Out URL out URL -This URL will be called just before a user logs out to log them out of their company account. Some providers may choose not to support this.
Client Secret secret - This is the most sensitive piece of data entered on this page. The company must provide this by secure means (E.G., a Client Portal client portal message). Never share this by unsecure means. After populating this field and saving, it's not possible to view the value.
Endpoints
...
These may be populated from the Metadata URL or entered.
...
Authorization Endpoint If a username is entered on the login screen of a user that has an email with a suffix matching one of the provided suffixes, they will be sent to this address. They will then log in to their company account and be sent back to InPay with a code.
Sharing Details with Clients and Logging
After saving the setup for the first time, ensure that this URL loads showing a login page. If not, there will be an issue with the setup on the clients side.
Sharing details with clients and logging
To easily confirm the correct configuration has been entered with a client. Click the Show Plain Details button.
Once a user is returned from the Authorization Endpoint, the request will be logged showing any issues.
FAQAnchor FAQ FAQ
| FAQ | |
| FAQ |
Unable to get claims
...
First try checking Validate Issuer. The claims returned are affected by this setting.
User can't login by SSO
If a user is unable to login by SSO once enabled, first:
- Check the log for any error messages to forward to support
- Check that the users email address is correct and ends with the text in Email Suffix 1 or Email Suffix 2
- Advise the user to register
- email suffix
If they're using Azure (the meta data url will start with login.microsoft...), are still having issues and you're seeing large amounts of text in the log. Ensure the client has added the email claim by sending these instructions:
...
Once they've completed these steps, set the Email Claim and Unique Id Claim in InPay to email.
Do you support SAML or SAML 2.0?
No, but most identity providers can support OAuth 2.0 or OpenId Connect.
...
- "google openId Connect": https://developers.google.com/identity/protocols/oauth2/openid-connect
- "oracle idcs openid connect": https://blogs.oracle.com/developers/authenticating-users-with-oracle-idcs-via-openid-connect-and-micronaut
The client would like some instructions
See Single Sign On, this will be of use even if they are using a different provider.
...
...
First confirm the Payslip Portal users saved email address is correct. If so, forward the error messages to the company's internal IT department.
Error message showing token response with no email
This may be that the claim is not being returned. Update the Authorization End Point to request the email scope: scope=openid+email
The full Authorization End Point would then be similar to https://SSOPROVIDER.COM/oauth2/default/v1/authorize?response_type=code&client_id=000000000000000&scope=openid+email&redirect_uri=https://inpay.es.rsmuk.com/payslipportal4/login.aspx&nonce=&state=
How do I login without entering my username?
Once a user has logged in once, their username will be populated on subsequent attempts (it’s stored in a cookie).
The closest we can get to populating on the first attempt is to put the username into the address E.G. https://inpay.es.rsmuk.com/payslipportal4/?username=support@in-time.co.uk
We don’t currently support IdP-Initiated SSO. This is where they would have an address for their SSO provider E.G. inpay.es.rsmuk.com/payslipportal4/?sso=CompanyName