INUBIT as an Identity Provider
This section demonstrates how INUBIT can be used as an identity provider.
|
The use of INUBIT is intended to be only a temporary solution and should only be deployed in production in consultation with your project team. |
Prerequisites
To use INUBIT as an identity provider, the BPC INUBIT Workflows must be installed.
Configuration (JAAS)
A new backend Connection of type identity_provider is created.
The following values must be set there.
| Setting (Key) | Group | Value | Description |
|---|---|---|---|
Module_Name |
module |
idp-INUBIT |
Assign a descriptive and unique name |
IdentityProvider |
config |
INUBIT |
Use INUBIT as the Identity Provider |
IdentityProvider_URL |
config |
http://INUBITSERVER:INUBITPORT/ibis/servlet/IBISHTTPUploadServlet/rest/authentication |
URL for the authentication HTTP connector in the BPC INUBIT workflow |
IdentityProvider_SelfServiceURL |
config |
http://INUBITSERVER:INUBITPORT/ibis/servlet/IBISHTTPUploadServlet/rest/uss |
URL to the User Self Service endpoint |
|
You should use*http*s** for the connection to INUBIT to avoid transmitting credentials in plain text. |
Special Features
When authenticating against INUBIT, all of a user’s process roles are added as roles, and all of their user groups are added as permissions inubitUserGroup_BENUTZERGRUPPENNAME.
INUBIT as an IdP does not allow for the configuration of customer- or project-specific permissions or organizations in addition to the standard INUBIT permissions.
These can be generated from roles, for example, via IdentityProvider_Mappings.
