Accton supports several authentication methods for connecting to your Qlik Sense connector (Server). Each method and the information it requires is described below. If you need help, contact our support team using the Help Request button in the Accton menu.
Common fields
These fields are required for all authentication methods:
| Item | Description | UI |
|---|
| Authenticate method | Authentication method used to connect to the Qlik Sense Server (JWT / Header / Header + Okapi2) | drop-down list |
| Domain | Domain used for report embedding | input field |
| Host | Base URL of the Qlik Sense Server | input field |
| BI username | Username used to access Qlik Sense reports | input field |
| API prefix | Prefix for API paths (optional) | input field |
1. JWT
Used to authenticate via a JSON Web Token, signed using an uploaded PEM certificate.
| Item | Description | UI |
|---|
| PEM certificate | Certificate file used to sign and verify the JWT | file input |
Used to authenticate by passing the authenticated username in a custom HTTP header.
| Item | Description | UI |
|---|
| User header name | Name of the HTTP header used to pass the authenticated username | input field |
Used the same way as Header, with an additional Okapi2 (OAuth2) client configured to obtain an access token for the request.
| Item | Description | UI |
|---|
| User header name | Name of the HTTP header used to pass the authenticated username | input field |
Okapi2 config
| Item | Description | UI |
|---|
| Host | Base URL of the Okapi2 OAuth2 token endpoint | input field |
| Client ID | OAuth2 client ID used to request an access token | input field |
| Client secret | OAuth2 client secret used to request an access token | input field |
| Scope | OAuth2 scope(s) requested for the access token | input field |
| Action | Description |
|---|
| Save | Saves the entered credentials for this connection |
| Cancel | Discards changes and closes the form |
| Clear | Clears all entered values from the form |