Configuring Outbound Provisioning Connectors for an Identity Provider
You can configure the WSO2 Identity Server to provision users to external applications. See the Identity Server Architecture for more information on how this process fits into the overall picture
You can configure outbound provisioning connectors by expanding the relevant section.
In addition to this, you can also create custom connectors that are added to the list of outbound provisioning connectors once created.
Configuring Google provisioning
This configuration involves setting up the Identity Server to send provisioning requests to Google applications.
Expand the Google Provisioning Configuration form and fill in the following fields where relevant.
Field | Description | Sample value |
|---|---|---|
Enable Connector | Selecting this enables identity provisioning through the Google domain. | Selected |
Google Domain | The name of the Google domain used to provision users. |
|
Primary Email | Claim URI which will be used to retrieve primary email address for the account to be created. This must be a claim that is available and local in the Identity Server. |
|
Given Name | Claim URI which will be used to retrieve given name attribute for the user. This must be a claim that is available and local in the Identity Server. |
|
Family Name | Claim URI which will be used to retrieve family name attribute for the user. This must be a claim that is available and local in the Identity Server. |
|
Service Account Email | This email is used for authentication purposes. |
|
Private Key | Browse and attach the private key from your local machine. This is the PKCS12 private key generated at the service account creation |
|
Administrator's Email | This is the email of the administrator who owns the service account in the Google Domain specified. Provisioning takes place using this email, so specifying this here serves as a means for authentication. |
|
Application Name | This is the name of the application which is used to represent the Google connector. |
|
Google Outbound Provisioning pattern | This pattern is used to build the user id of Google domain. Combination of attributes UD (User Domain), UN (Username), TD (Tenant Domain) and IDP (Identity Provider) can be used to construct a valid pattern. This is a way to differentiate following scenarios: |
|
Google Provisioning Separator | This is used to separate the values that you configure in the Google Outbound Provisioning pattern. | For this, it is better to use a character that is not normally used in the user domain/username/tenant domain/idp name. For example: "_" |
Configuring Salesforce provisioning
This configuration involves setting up the Identity Server to send provisioning requests to Salesforce. See Outbound Provisioning with Salesforce for more information on how this is configured from end to end.
Expand the Salesforce Provisioning Configuration form.
Fill in the following fields where relevant.
Configuring SCIM provisioning
The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in the WSO2 Identity Server easier. Identity provisioning is a key aspect of any identity management solution and, as such, is very relevant to SCIM. In simple terms, it is to create, maintain and delete user accounts and related identities in one or more systems or applications in response to business processes that are initiated either by humans directly or by automated tasks.
This configuration involves setting up the Identity Server to send provisioning requests to an external application that supports SCIM. See Outbound Provisioning with SCIM for more information on how this works in a typical scenario.
Expand the SCIM Provisioning Configuration form.
Fill in the following fields where relevant.
Configuring SPML provisioning
The Service Provisioning Markup Language (SPML) is the open standard for the integration and interoperation of service provisioning requests. The goal of SPML is to allow organizations to securely and quickly set up user interfaces for Web services and applications, by letting enterprise platforms such as Web portals, application servers, and service centers generate provisioning requests within and across organizations
This configuration involves setting up the Identity Server to send provisioning requests to an external application that supports SPML. See Outbound Provisioning with SPML for more information on how this works in a typical scenario.
Expand the SPML Provisioning Configuration form.
Fill in the following fields where relevant.
See Outbound Provisioning for more information on configuring user stores and service providers for outbound provisioning.