Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
This article describes how to ensure that card encoding works properly, when an authenticating reverse proxy, such as Smart ID Digital Access component (Hybrid Access Gateway), is used in front of Smart ID Identity Manager (PRIME). Certain PRIME . Certain Identity Manager endpoints must be allowed, as is described below.
Example setup
Expand | ||||
---|---|---|---|---|
| ||||
In the following examples, it is assumed that you access PRIME Explorer access Identity Manager Operator via the following external URL of the reverse proxy:
...which then connects to the internal Prime internal Identity Manager server:
|
Step-by-step instruction
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
To enable Card SDK to download the JPKIEncoder, you must allow the download endpoints for JAR files:
|
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
The CA connectors of PRIME of Identity Manager use a session ID cookie embedded in the cardjob to allow the JPKIEncoder to authenticate any CA requests it has to make. The reverse proxy's authentication layer must allow the CA connector cookies without authentication. Calls will still be authenticated, via PRIME via Identity Manager itself.
|