Error in API URL call through Qlik Application Automation in SaaS

[sanekagr2]

Hi everyone, 

I' trying to send a POST URL call via Qlik Application Automation:

https://qlik.dev/apis/rest/identity-providers/#post-v1-identity-pro

/v1/identity-providers

Body of the call:

{

    "protocol": "jwtAuth",

    "provider": "external",

    "description": "JWT Identity Provider",

    "tenantIds": ["ay...........oH"],

    "clockToleranceSec": 50,

    "options": {

        "issuer": "che............om",

        "jwtLoginEnabled": true,

        "staticKeys": [

            {

                "kid": "c........kid",

                "pem" "-----BEGIN PUBLIC KEY-----

MIIBIjANBgkqhkiG9.........c

rwIDANNN

-----END PUBLIC KEY-----":

            }

        ]

    }

}

I'm receiving a 400 error::

The issue seems to be with the body, likely related to the PEM format.

How can I resolve this?

Thanks!

[eyalnir_qlik]

Hello @Daniele_Purrone 

Can you kindly advise on this matter ?

Thanks, 

Eyal 

[Daniele_Purrone]

Hi @sanekagr2 , you are mentioning a POST, but I see a GET method in the response. 
Can you share screenshots of the block (all tabs)?
Of course, you can obscure sensitive data.

[sanekagr2]

Hi @Daniele_Purrone,

Thank you for the response,

I'm sending the request using POST, but for some reason, the log shows an error with a GET method

[Dave_Channon]

If you're creating a JWT IdP, the trick is to strip line breaks - see an example posted at https://qlik.dev/examples/manage-examples/identity-provider-create/ in the JWT IdP box.

One other way of doing this to verify is creating it in the admin console & monitoring the request that gets sent to the API via developer tools.

[sanekagr2 · Accepted solution]

Thanks,

We removed the line breaks and used the same PEM value that worked in a regular REST request but didn’t work in the block URL.

In the end, we found a solution by configuring the IDP creation block.

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-creating-oidc-i...

[Daniele_Purrone]

Good to know, thanks @sanekagr2 !