Configure Trading Partner/Member IdP
When setting up user authentication for you partners, you can configure the service in a way that they either create and use Smart Trading accounts or use their identity providers (IdPs).
Note When you configure your trading partner identity provider, all your partners are required to sign in through their identity provider(s). If you do not integrate your trading partner's identity provider authentication, all your partners are required to sign in using their Smart Trading account credentials.
You can authenticate your trading partners in Smart Trading Cloud services with your trading partner identity provider (IdP) that supports the Security Assertion Markup Language (SAML) 2.0 and OpenID Connect (OIDC) federated protocols. Thus, allowing your trading partners to access Smart Trading Cloud services, for example, Onboarding and Testing Cloud Service without having to create a Smart Trading account. Learn more about SAML and OIDC federation and the authentication flow for your users and trading partners.
Follow the steps given in this section to configure your trading partner identity provider though the SAML or OIDC connection types.
Prerequisites
Before you start configuring your trading partner identity provider though the SAML or OIDC connection types, make sure that the following information is available:
- IdP Metadata: an XML file with your SAML identity provider metadata to fill in the configuration form automatically.
- Discovery Uri: The URL where an OpenID server publishes its metadata and which returns a JSON listing of the OpenID/OAuth endpoints, available scopes and claims, public keys used to sign the tokens, and other details.
Or if you do not have the file with metadata, you will need to enter the following details manually:
- IdP Information:
- SSO URL: The single sign-on endpoint of your trading partner identity provider to which a browser redirects a user to sign in.
- Logout URL: The remote logout URL where the identity provider will send logout requests and responses. Smart Trading Cloud will redirect users to this URL after they sign out.
- Entity ID: The URL of the identity provider's metadata document reflecting the organization that owns the identity provider. An entity ID is a unique name that distinguishes system entity in metadata, such as an identity provider (IdP) or an service provider (SP), from any other entity.
- Signature Verification Certificate: Your trading partner identity provider's X.509 public key certificate that Smart Trading Cloud must use to validate assertions' correctness.
Configure integration of a trading partner identity provider in Smart Trading Cloud
- Go to Smart Trading Cloud at https://auth.edifecsfedcloud.com and sign in as an account administrator.
Watch the video tutorial on how to get started with Smart Trading Cloud.
- Go to Connections (
on the left navigation bar).
- Click
Trading Partner / Member IdP.
- On the Identity Provider (IdP) Configuration page, click + Add.
- On the Create New IdP page, enter the line of business, such as Commercial, Medicare, or Medicaid.
- Select SAML or OIDC connection type.
For the SAML connection type, provide identity provider information either through: IdP Metadata: Click Upload Metadata to upload XML file with your trading partner SAML identity provider metadata. -Or- The following: - In SSO URL, enter the single sign-on endpoint of your identity provider to which a browser redirects a user to sign in.
- Select to use HTTP-POST bindings if you want the SAML protocol messages to be transferred within the base64-encoded content of an HTML form control. By default, the HTTP Redirect binding is used.
- In Logout URL, enter the remote logout URL where the identity provider will send logout requests and responses. Smart Trading Cloud will redirect partner users to this URL after they sign out.
- Select HTTP-POST binding for logout if you want the SAML protocol messages to be transferred within the base64-encoded content of an HTML form control for logout.
- In Entity ID, enter the URL of the identity provider's metadata document reflecting the organization that owns the identity provider.
- In Signature Verification Certificate, enter the trading partner identity provider's X.509 public key certificate that Smart Trading Cloud must use to validate assertions' correctness.
For the OIDC connection type, enter the URL of the discovery endpoint from which the clients will be reading the available scopes and claims, public keys used to sign the tokens, and other details.
- Click Save.
You can find the information (SSO and logout URLs) on the configured trading partner identity provider on the left side of the page.
Edit or delete a trading partner IdP
- Go to Connections (
on the left navigation bar).
- Click
Trading Partner / Member IdP.
- On the Identity Provider (IdP) Configuration page, click on the IdP you want to edit or delete.
- To edit the IdP configuration, click
. Edit the configuration and click Save.
- To delete the IdP, click
.
Assign a service
- Go to Connections (
on the left navigation bar).
- Click
Trading Partner / Member IdP.
- On the Identity Provider (IdP) Configuration page, click on the IdP you want to assign a service to.
- On the right pane, under the identity provider name, click +Add Service.
- In the Add a Service pane, in Service, from the drop-down list, select a service for which you configured integration of the trading partner identity provider (for example, Onboarding and Testing Cloud Service).
- Provide Client ID and Scope(s).
- Under Attributes, enter the attribute names that are associated with the authenticated user based on the service provider's requirements. The attributes may vary based on the selected service.
- Click Save.
The information on the added Smart Trading Cloud service appears on the right side of the page, in the Assigned Services (CountOfServices) section, where you can find the following details:
- Callback URL: The URL to which the SAML Authentication Assertion is sent from the service provider.
- RelayState: The URL parameter that is used to coordinate messages and actions of the identity and service providers, for example, to allow the identity provider (through which single sign-on (SSO) was initiated) to indicate the URL of a desired resource when communicating with a service provider, in other words, to where send the response back.
- Attributes: The attribute names that are associated with the authenticated user based on the service provider's requirements.
Configure your trading partners identity provider
To configure your trading partners identity provider, go to your trading partners identity provider settings and add a Smart Trading Cloud service, for example, Onboarding and Testing Cloud Service as a service provider using the metadata (the saml-conf.xml file) (consult your identity provider documentation on how to set up a new trusted application). You can also use SAML2 General Settings.
Workflows with single sign-on (SSO)
SSO enabled
The following workflow occurs when single sign-on is enabled.
- Your partner user goes to an identity provider selection screen with identity providers using the link you provided.
- The partner user selects a required identity provider through which they will sign in to a Smart Trading Cloud service.
- The identity provider prompts the partner user for their credentials.
- If the partner user enters valid credentials, they get authenticated through your trading partners identity provider.
- The partner user is redirected to a Smart Trading Cloud service and is logged in.
IDP-initiated SSO enabled
For this case, in your trading partner's identity provider, IDP-Initiated SSO URL name should be set up.
- Your partner user goes to an IDP-Initiated SSO URL. The partner user is redirected to the Identity Provider’s sign-in screen.
- The identity provider prompts the partner user for their username and password.
- If the partner user enters valid credentials, they get authenticated through your partners identity provider.
- The partner user is redirected to a Smart Trading Cloud service and is logged in.
|
|