---
title: "Client apps need more information from the Auth server"
slug: "dpo-client-apps-need-more-information-from-the-auth-server"
updated: 2026-10-27T20:13:21Z
published: 2026-10-27T20:13:21Z
canonical: "docs.onespan.com/dpo-client-apps-need-more-information-from-the-auth-server"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Client apps need more information from the Auth server

The API Server acts like a gatekeeper on the amount of information that is returned from the Authentication Server to the App SDK. If your app specifically requests additional information, such as the user's device or the authenticator and authentication method that they used, then you also need to modify the API Server's response filter to allow that information to reach the App SDK.

Export an existing tenant-specific configuration object called Main and modify it to configure the response filter. The command below shows how to export this object from the database for the default tenant.

```plaintext
./nnl-mgmt.sh apiserver export -tenantid default -type Main -name Main -file Main.json
```

Edit Main.json, the file's contents are similar to what's shown below.

```plaintext
{
    "mfas_response_filter":{
        "additionalInfo":{
            "device":true,
            "authenticatorsResult":[
                {
                    "handle":true
                }
            ]
        }       
    },
    "origin_allowlist":[
    ]
}
```

Response filter configuration uses a JSON structure that specifies which data the API Server should allow through. This structure is assigned to an attribute called mfas_response_filter. See [Response Filter Configuration](/dpoa/docs/s3suite94-main-1#response-filter-configuration) to create a response filter configuration that you can assign using either the Admin Console or upload using nnl-mgmt.sh.

Main.json also contains the entry origin_allowlist that contains the URLs for trustworthy web client apps. Examine that to make sure those are web apps you want to allow. See [My Web Client Apps Have a Different Origin than the API Server](/dpoa/docs/s3suite94-my-web-client-apps-have-a-different-origin-than-the-api-server-1).

After you have made your modifications, use one of the instructions below to update the information.

#### Using the Admin Console

1. In the Admin Console, login and, if needed, switch to the desired tenant. Navigate to **Configuration > API Server >** **Main**.

![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/image(212).png?sv=2026-02-06&spr=https&st=2026-10-29T02%3A43%3A30Z&se=2026-10-29T03%3A43%3A30Z&sr=c&sp=r&sig=BRSRmLur0txhybQgFZdUYjY9OC9kmsvsp9IJ%2BF%2F44xQ%3D)

1. Click the value for **Server response filter**. Enter the JSON for mfas_response_filter.

#### Using nnl-mgmt.sh

The apiserver import command expects a file containing an API Server Main configuration object, this needs to contain both the mfas_response_filter and origin_allowlist fields. Below is an example using nnl-mgmt.sh's apiserver import command to import a modified Main.json for the finance tenant.

```plaintext
./nnl-mgmt.sh apiserver import -tenantid finance -type Main -name Main -file Main.json
```

For details on apiserver import command, refer to [*API Server Configuration Commands*](/dpoa/docs/s3suite94-api-server-configuration-commands-1).