ScreeningRequest in Postman ZFS environment returns 401 Unauthorized

Question

Question by czernicki · Nov 20, 2019 at 09:01 PM · 401 unauthorized screeningrequest

ScreeningRequest in Postman ZFS environment returns 401 Unauthorized

I have started development for the Zero Footprint screening with the provided keys. When testing in Postman the Get groups API works fine, then I use the returned group id for the ScreeningRequest but I am getting status 401 Unauthorized.Please advise. groups.png screening.png

groups.png (205.9 KiB)

screening.png (159.7 KiB)

0

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2019-11-27T06:20:35Z

REFINITIV

Best Answer

Answer by Prabhjyot · Nov 27, 2019 at 06:20 AM

@czernicki,

Thank you for the confirmation.

The key(s) were not in sync with the cloud platform. Hence, you were receiving Error 401. We have made the necessary changes to sync the key(s) with the cloud platform and the issue has been now resolved.

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 2 · 2019-11-21T04:36:01Z

REFINITIV

Answer by Prabhjyot · Nov 21, 2019 at 04:36 AM

@czernicki,

Thank you for your request.

Can you please share the postman console logs [ Request / Response Headers ] for the failed API call to investigate on the cause of the error?

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 3 · 2019-11-21T14:34:33Z

Answer by czernicki · Nov 21, 2019 at 02:34 PM

Console log attached log.txt

log.txt (1.3 KiB)

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 4 · 2019-11-22T12:49:08Z

REFINITIV

Answer by Prabhjyot · Nov 22, 2019 at 12:49 PM

@czernicki,

Thank you for sharing the logs.

Can you please check API credentails whic you are using for consuming the API?

Please login to UI > Go to Admin > Click on Users > Select Username > On the right section, you should be able to see the credentials for the API user.

Can you please confirm if the credentails which you are using is correct and as per the account?

Please let us know if this helps.

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 5 · 2019-11-22T13:24:28Z

Answer by czernicki · Nov 22, 2019 at 01:24 PM

I checked the keys, they are exactly the same in the UI and the Postman environment variables, sending the screenshots so you can see them, can you test with my keys? Maybe they are not correctly setup on your end. UIkeys.png PostmatZFSEnvironment.png

uikeys.png (7.0 KiB)

postmatzfsenvironment.png (22.9 KiB)

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 6 · 2019-11-25T10:33:00Z

REFINITIV

Answer by Prabhjyot · Nov 25, 2019 at 10:33 AM

@czernicki,

Thanks for sharing the details.

Can you please let us know if you are facing the issue with any specific API call or all the API calls ?

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 7 · 2019-11-25T15:55:20Z

Answer by czernicki · Nov 25, 2019 at 03:55 PM

The issue is with the screeningRequest only, when I run the groups it works fine, I have attached the image of this api on the first post of this thread. The difference I see is that the groups uses the gateway-host , while screeningRequest uses zfs_gateway-host, that is how the API was automatically set when importing the zero footprint postman collection.

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 8 · 2019-11-26T12:08:22Z

REFINITIV

Answer by Prabhjyot · Nov 26, 2019 at 12:08 PM

@czernicki,

Thank you for confirming.

Could you please try again and let us know if this is working fine now?

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 9 · 2019-11-26T13:26:26Z

Answer by czernicki · Nov 26, 2019 at 01:26 PM

The API is working fine now it returned status 200, was it a setup issue on your end? Thanks for your support on this matter.

0 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 10 · 2019-12-04T16:13:55Z

Answer by suveer.singh · Dec 04, 2019 at 04:13 PM

Im facing the exact same issue as described before. I received new credentials(Key + Secret) today, postman collection was working fine previously. GetMyTopLevelGroups endpoint is working. ScreeningRequest specifically is not working

0 Show 1 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

REFINITIV

Prabhjyot ♦♦ · Dec 05, 2019 at 05:59 AM 0

Share

@suveer.singh,

Thank you for reporting the issue.

I will get back to you on the query which you have posted separately.

ScreeningRequest in Postman ZFS environment returns 401 Unauthorized

10 Replies

Watch this question

Related Questions