Slack Integration Profile Creation Failure with Connection Validation Errors Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } A user encountered failure during Slack integration profile creation, resulting in connection validation errors. Connection validation is not successful. Please check connections and credentials and try again.User does not have the required role or write access, or conditions not met for table: samp_sw_subscription_profile The error message indicated connection validation failure, and the user confirmed official documentation steps without success. The issue persisted despite verifying endpoints, credentials, and Slack application configurations. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } sn_sam_saas_int 15.0 com.sn_sam_workspace8.0 Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. The integration profile was incorrectly mapped to a custom credential alias instead of the OOB credential record, causing configuration mismatches. 2. Redundant or unused Slack workspace tokens contributed to configuration conflicts, leading to validation failures. 3. Permission or scope misconfigurations in the Slack application may have blocked proper authentication flow. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } - Update the URLs and check the org-readiness setting Steps:1. Open the Application Registry record for Slack.2. Open the record and replace the following: Authorization URL:https://slack.com/oauth/v2/authorize Token URL: https://slack.com/api/oauth.v2.access Refresh Token URL: https://slack.com/api/oauth.v2.access3. Save the record.4. As a Slack administrator, open the Credential record and click the Get OAuth Token related link.5. The customer must repeat the same procedure for the Slack workspace connections as well.6. Ensure that the customer's Slack OAuth app does not have Enable org-readiness enabled, as this setting prevents users from requesting admin scopes. - Ensure that the user who verifies the connection has the appropriate roles and permissions 1. ServiceNow Admin Role（admin）2. IntegrationHub Role (flow_operator or flow_designer)3. OAuth Right To register an OAuth provider in ServiceNow, the user must have sufficient permissions to access System OAuth > Application Registry.4. Slack Admin Role（Workspace Admin or Org Admin） The user must have sufficient permissions to install the Slack application in the workspace and approve the required OAuth permissions. - Additional steps required for PRB1855153 1. Delete the admin scope from OAuth Entity Profile Scopes and OAuth Entity Scopes: oauth_entity_profile_scope_list oauth_entity_scope_list 2. Update the OAuth API Script field in the Application Registry to OAuthUtilSlackEnterprise: oauth_entity_list - If the following error occurs when the scheduled job is executed Last refresh failed at YYYY-MM-DD HH:MM:SS. Check the job logs and have a ServiceNow admin re-run the failed jobs. If the problem persists, the admin should check OAuth credentials and retrieve new tokens.Invalid alias override. Alias are not found in flow slack_update_user_activity. Please perform the following checks:1. Update or delete any workspaces that do not have a connection, and then try running the activity job again.2. If the Connection Alias field is empty in the Slack Workspace Token table, populate it with the appropriate connection alias. - If the error persists Verify that the integration profile is mapped to the correct OAuth Entity Profile and Credential record(sn_slack_ah_v2.Slack_Enterprise). Ensure that it uses the OOB credential record rather than a custom alias.