topic Re: Azure Active Directory users - Incorrect padding in Cortex XSOAR Discussions

Azure Active Directory users - Incorrect padding

Matt-Thomas — Mon, 07 Apr 2025 17:39:08 GMT

I am trying to connect an Azure AD (EntraID) to so that I can use the user-disable playbooks. However, each time I try to authenticate i get the below error

Error in Microsoft authorization: Incorrect padding Please check authentication related parameters. Traceback (most recent call last): File "<MicrosoftApiModule>", line 1358, in encrypt File "/usr/local/lib/python3.12/base64.py", line 88, in b64decode return binascii.a2b_base64(s, strict_mode=validate) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ binascii.Error: Incorrect padding (85)

I am using the Client_ID, Tenant ID, and Client Secret. The same settings work in postman and in the office 365 integration, so I am pretty sure the client_id, secret, and permissions are correct.

I also have a Demo Azure environment that is working fine using the same setup.

Any Ideas on what may be happening?

Thanks,

Re: Azure Active Directory users - Incorrect padding

Ivetto — Mon, 14 Apr 2025 19:15:39 GMT

Hello,

The error of incorrect padding points me to thinking that there might be extra white spaces or unknown characters being passed on the credentials. Please double check this and if it still doesn't work then I recommend you create a case with our Support team.

Re: Azure Active Directory users - Incorrect padding

mattem — Fri, 08 Aug 2025 04:26:23 GMT

I have a similar problem, though with the Azure Active Directory Groups XSOAR integration.

We have successfully configured Azure Active Directory Users XSOAR integration though. If I can discern the difference between the two, I'll post here with the solution.

Re: Azure Active Directory users - Incorrect padding

Matt-Thomas — Thu, 28 Aug 2025 19:58:55 GMT

I fixed this by clicking the "Use a self-deployed Azure application" button

Re: Azure Active Directory users - Incorrect padding

mattem — Thu, 28 Aug 2025 23:29:33 GMT

Oops, I'd forgotten to post again once I found the solution.

Just like Matt-Thomas, my integration config was successful after I checked the "Use a self-deployed Azure application" checkbox.

I've noticed quite a bit of variation in terminology and layout in the XSOAR Integrations for Microsoft services, and I think XSOAR would benefit from having uniform terms and layout in the Integration, along with more specific language being used in the documentation.