This article describes how to ensure that card encoding works properly, when an authenticating reverse proxy, such as Smart ID Digital Access component, is used in front of Smart ID Identity Manager. Certain Identity Manager endpoints must be allowed, as is described below.

Example setup

In the following examples, it is assumed that you access Identity Manager Operator via the following external URL of the reverse proxy:

https://prime.with.hag/prime_explorer/

...which then connects to the internal Identity Manager server:

https://prime.internal:8443/prime_explorer/

Step-by-step instruction

To enable Card SDK to download the JPKIEncoder, you must allow the download endpoints for JAR files:

Enable everything in the /eclnt/lib/ folder to pass through without authentication. For example:
Example with Digital Access component as reverse proxy
https://prime.with.hag/prime_explorer/eclnt/lib/* => https://prime.internal:8443/prime_explorer/eclnt/lib/*
This covers the following parts:
/prime_explorer/eclnt/lib//filelist - list of JARs to download
/prime_explorer/eclnt/lib//*.jar - the actual JAR files listed in filelist

Make sure you use the correct syntax for your reverse proxy.

The CA connectors 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 Identity Manager itself.

Enable everything in the /ws/ca_connectors/ folder to pass through without authentication. For example:
Example with Hybrid Access Gateway as reverse proxy

Make sure you use the correct syntax for your reverse proxy.

Make sure that cookies, at least JSESSIONID, are forwarded on these endpoints.

Nexus Documentation

Card encoding with authenticating reverse proxy

Step-by-step instruction