Setup WSO2 Identity Server as a Federated Authenticator¶
WSO2 Identity Server 7.1.0 includes B2B organization support. The following instructions detail how to configure it as a federated authenticator for WSO2 API Manager.
Configure WSO2 Identity Server¶
- Download WSO2 Identity Server 7.1.0.
- Add following configurations in the
/repository/conf/deployment.toml file. -
Start WSO2 Identity Server with a port offset. Port offset is required only if you are running both API-M and IS 7.x in the same JVM.
sh wso2server.sh -DportOffset=1
-
Log in to the IS Console at https://localhost:9444/console and create a new application.
- Select "Traditional Web Application" and complete the form.
- Set the Redirect URL to https://localhost:9443/commonauth
-
Select ‘Allow sharing with organizations’ option.
-
Once the application is created, go to the 'Protocol' tab and copy the Client ID and Secret for later use.
-
Under
User Attributes
section, selectRoles
-
Under
Subject
section, selectAssign alternate subject identifier
and selectUsername
. -
Under User
Roles
section, add Application rolesdevportal
,publisher
,creator
,admin
-
Go to the
User Management
section, navigate to theUsers
tab, and create three users—one for each portal. -
Go to the
Roles
section underUser Management
section and assign application roles to users. (Check audience column and get the application/roles) -
Select role and go to the
Users
tab and assing users to the role. In this example admin → orgadmin publisher, creator → larry devportal → david -
Now let's create organizations. For that select
Organization
and create a couple of new organizations. Note down the organization Ids -
Select the organization and click
Switch to Organization
. -
Under
Users
section inUser Management
add a new user. Let’s sayemily
androbert
-
Under
Roles
section inUser Management
find the previously createddevportal
role and select it. SelectUsers
tab and set the user to this roleNote
Organization restriction capability is not supported in the Admin and Publisher portals in this release. To prevent organization users from logging into these portals, do not assign them Admin or Publisher/Creator roles to the users in sub organizations.
-
Similarly create user in another organization and assign developer role.