Password length not accepting in Basic AuthCode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2023 03:09 AM
I have to integrate ServiceNow and Jira and for that I am using basic authentication. In that the length of API Token from Jira is very large and is not accepting by ServiceNow . It shows the error message as follows -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2024 07:40 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2025 09:20 AM
Also change the sys_auth_profile_basic table's password length to 512. This is what finally worked for me when configuring an Outbound REST message's Basic authentication.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2025 11:01 AM
Hi @surbhi_123 ,
Options to fix
1. Use “Basic Auth” headers directly in the REST Message (workaround)
Don’t save the long string in the credential record.
In your REST Message, set an HTTP Header:
Name: Authorization Value: Basic <base64encoded(email:api_token)>You can generate the Base64 string externally (or with a background script in SN) and paste it here.
2. Use “HTTP Authentication Profile – OAuth 2.0” (recommended)
Atlassian supports OAuth 2.0 for integrations.
This avoids token length issues, is secure, and future-proof.
3. Use Connection & Credential Aliases
Store the token in an encrypted field (Credential record), and reference it in your REST Message.
This way you don’t manually paste long strings into the REST profile.
