Developer

Hello

In case anyone else out there is having problems running the AOS-CX Postman collection against a virtual CX, here is a solution that I came up with. The collection comes with a script that looks for a header in the response object of a successful authentication called 'X-Csrf-Token', then sets the value of that header as the token. Running this against a virtual CX failed. After a bit of digging I noticed that a successful authentication set a set-cookie header that contains the token. Modifying the Pre-request script to look for a header value that starts with 'user' and using that as a bearer token seems to work. Here's the code:

        }, function (err, response) {            if (response.code == 200){                token = null                responseJSON = JSON.parse(JSON.stringify(response))                Object.entries(responseJSON.header).forEach(([key, value]) => {                    key = value.key                    value = value.value                    //console.log(`header: ${key} - ${value}`)                    if (value.startsWith("user")){                        console.log('Login Successful. Succcessfully fetched new API token.')                        console.log(`${value}`)                        token = value                        pm.environment.set("token", token);                        pm.request.headers.add({                            key: "x-csrf-token",                            value: pm.environment.get("token")                            });                    }                });

Replace lines 30-48 in the pre-request script with that. 

I don't know if that will work with other CX versions

Hi Allen,

Do you have try with new OVA image? (10.07 is very old and not longer supported)

Hello

In case anyone else out there is having problems running the AOS-CX Postman collection against a virtual CX, here is a solution that I came up with. The collection comes with a script that looks for a header in the response object of a successful authentication called 'X-Csrf-Token', then sets the value of that header as the token. Running this against a virtual CX failed. After a bit of digging I noticed that a successful authentication set a set-cookie header that contains the token. Modifying the Pre-request script to look for a header value that starts with 'user' and using that as a bearer token seems to work. Here's the code:

        }, function (err, response) {            if (response.code == 200){                token = null                responseJSON = JSON.parse(JSON.stringify(response))                Object.entries(responseJSON.header).forEach(([key, value]) => {                    key = value.key                    value = value.value                    //console.log(`header: ${key} - ${value}`)                    if (value.startsWith("user")){                        console.log('Login Successful. Succcessfully fetched new API token.')                        console.log(`${value}`)                        token = value                        pm.environment.set("token", token);                        pm.request.headers.add({                            key: "x-csrf-token",                            value: pm.environment.get("token")                            });                    }                });

Replace lines 30-48 in the pre-request script with that. 

I don't know if that will work with other CX versions