Info |
---|
This article is valid from Nexus PRIME 3.6. |
This article describes how to connect
...
Smart ID Identity Manager to the
...
Smart ID Digital Access component Extension Programming Interface (XPI), to enable provisioning of users and
...
...
App profiles.
Prerequisites
Expand | ||
---|---|---|
| ||
|
...
|
...
|
...
|
...
|
...
|
...
Step-by-step instruction
Expand | ||
---|---|---|
|
...
| |
To be able to use the Digital Access XPI interface |
...
, an SSL server certificates needs to be provided. For demo use cases it’s sufficient to create a self-signed certificate including private keys. Skip these steps if a real server certificate exists.
|
...
|
Expand | ||
---|---|---|
| ||
To install the server certificate in |
...
Digital Access |
...
component:
|
...
|
...
|
...
|
Expand | ||
---|---|---|
| ||
The server certificate needs to be added to the trust store, to make the |
...
Identity Manager server trust the certificate during the XPI call.
|
...
|
Expand | ||
---|---|---|
| ||
An Authentication Method of type Password must be set up, so |
...
that Identity Manager can authenticate against |
...
Digital Access |
...
XPI.
|
...
|
...
|
...
|
...
|
Expand | ||
---|---|---|
| ||
To authenticate to the XPI with username and password, a delegated administrator must be defined. The user must be in the already connected user storage. See Add user storage in Digital Access for more information. To assign the delegated administrator role to a user:
|
...
|
...
|
Expand | ||
---|---|---|
|
...
|
...
| |
For |
...
Identity Manager to get access to |
...
Digital Access |
...
component over the XPI, the XPI must be enabled. To enable the |
...
Digital Access |
...
XPI:
|
...
|
...
|
...
|
...
title | Activate Hybrid Access Gateway in PRIME |
---|
Note |
---|
This task is only necessary for PRIME version 3.7.1 and earlier. From version 3.7.2, the HAG Settings option will be activated by default. |
To activate the HAG Settings option in PRIME Explorer under the Admin tab:
...
Add the following bean definition:
Code Block | ||||
---|---|---|---|---|
| ||||
<bean id="hagXPIContext" class="de.vps.act.frontend.admin.systemproperty.ContextVO" scope="prototype">
<property name="contextVOName" value="hagXPIContext"></property>
<property name="name" value="hag.xpi.settings"></property>
<property name="propertyVOs">
<list>
<bean name="hagXPIuserProperty" class="de.vps.act.frontend.admin.systemproperty.PropertyVO" scope="prototype">
<property name="name" value="user"></property>
<property name="text" value="hag.xpi.property.user" />
<property name="type"><util:constant static-field="de.vps.act.kernel.datatype.DataType.STRING" />
</property>
<property name="defaultValue" value="xpiadmin"></property>
</bean>
<bean name="hagXPIPasswordProperty" class="de.vps.act.frontend.admin.systemproperty.PropertyVO" scope="prototype">
<property name="name" value="password"></property>
<property name="text" value="hag.xpi.property.password" />
<property name="isSecretValue" value="true" />
<property name="type">
<util:constant static-field="de.vps.act.kernel.datatype.DataType.REF"/>
</property>
</bean>
<bean name="hagXPIAuthenticationMethodIdProperty" class="de.vps.act.frontend.admin.systemproperty.PropertyVO" scope="prototype">
<property name="name" value="authenticationMethodId"></property>
<property name="text" value="hag.xpi.property.authenticationMethodId" />
<property name="type"><util:constant static-field="de.vps.act.kernel.datatype.DataType.NUMERIC" />
</property>
<property name="defaultValue" value="3"></property>
</bean>
</list>
</property>
</bean>
|
To activate the hagXPIContext
bean, add it to the systemPropertyBuilder
bean in the same file:
...
title | Example: custom-beans-BIM.xml - Update systemPropertyBuilder bean |
---|
...
|
...
<property name="systemProperties">
<list>
<ref bean="hagXPIContext" />
<ref bean="smtpContext" />
...
<ref bean="tunnelServerContext" />
<ref bean="coreTemplateContext" />
</list>
</property>
</bean>
...
Expand | ||
---|---|---|
|
...
|
...
|
...
| |
To enter the |
...
Digital Access |
...
XPI credentials in |
...
Identity Manager:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Expand | ||
---|---|---|
|
...
|
...
|
...
| |
To define which data should be provision from |
...
Identity Manager to |
...
Digital Access, the settings in the |
...
Digital Access provisioning task must be adapted. For more information, see |
...
Standard service tasks in Identity Manager. The task is used in the |
...
Identity Manager processes that provision the data to |
...
Digital Access. There are processes available in the Base configuration package (BIM), called BaseProcActivateAndProvisionUserToHag and BaseProcDeactivateAndProvisionUserToHag. To adapt the settings in the |
...
Digital Access provisioning task, do the following for each process:
|
...
|
...
|
...
|
...
This article is valid from Nexus PRIME 3.6.
Related information
...
Additional information
Expand | ||
---|---|---|
| ||
...