Customer cannot save long API token password for Jira Spoke in credential record in ServiceNowIssue From 18 January 2023, Jira has extended the length of API tokens for Atlassian accounts. To increase security, Jira accounts no longer supports short token lengths. Due to this change, whenever users are trying to enter Jira account details for the ServiceNow Jira Spoke by creating a new credential profile under Basic Auth Credentials (refer https://docs.servicenow.com/csh?topicname=setup-jira-spk-opt2.html&version=latest) they are facing with the following notification: Action abort: Password value is too long and could be truncated after encryption. Please either reduce password length or increase field size. ReleaseAllCauseThe default length for the Password field used by the Jira Spoke is 255 characters. However, after password hashing this Jira API Token password character length might increase to more than 255 character in length.ResolutionYou need to increase the max password value to more than 255 to accomodate the extended character length. Test it with higher value and then check. Here is how to do that: On your instance 1. Go to -> System Definition -> Tables 2. Find the table 'discovery_credentials' by using filter with Name starts with 'discovery_credentials'. 3. Then find the Table Column 'Password', where it should have 'Max Length' as 255. 4. Change the value of the Max Length of the password field as per your requirement [Default Max length mentioned: 255] Picture-2: table Name: Picture-3: Table Column: 5. Then follow the same for basic_auth_credentials table. Related LinksManage API token for Jira: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/ How to setup Jira account: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0792632