{"id":1454,"date":"2023-10-05T18:46:30","date_gmt":"2023-10-05T18:46:30","guid":{"rendered":"https:\/\/www.versionsql.com\/help\/documentation\/error-messages\/failed-to-parse-supported-auth-schemes-the-operation-identifier-is-not-valid\/"},"modified":"2023-10-24T03:00:43","modified_gmt":"2023-10-24T03:00:43","slug":"failed-to-parse-supported-auth-schemes-the-operation-identifier-is-not-valid","status":"publish","type":"docs","link":"https:\/\/www.versionsql.com\/help\/documentation\/error-messages\/failed-to-parse-supported-auth-schemes-the-operation-identifier-is-not-valid\/","title":{"rendered":"Failed to parse supported auth schemes: The operation identifier is not valid."},"content":{"rendered":"

VersionSQL’s attempt to secure a connection via OAuth was blocked by an atypical response from Azure DevOps. This rare error may be triggered by unusual user account permissions. As a workaround, use a Personal Access Token (PAT) with Code: Read & Write permissions:<\/p>\n

    \n
  1. Navigate to Azure DevOps > User Settings > Personal Access Tokens.<\/li>\n
  2. Create a new token with Code: Read & Write<\/code> permissions.<\/li>\n
  3. Clear existing credentials from your VersionSQL connection and try connecting again.<\/li>\n
  4. Close the OAuth dialog when it appears and input your new PAT when prompted.<\/li>\n<\/ol>\n

    Note: If you are already using a PAT and see this error, ensure the token has not expired.<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":121,"menu_order":10,"comment_status":"closed","ping_status":"closed","template":"","meta":{"inline_featured_image":false,"footnotes":""},"doc_tag":[3],"class_list":["post-1454","docs","type-docs","status-publish","hentry","doc_tag-error"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs\/1454","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/comments?post=1454"}],"version-history":[{"count":8,"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs\/1454\/revisions"}],"predecessor-version":[{"id":1565,"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs\/1454\/revisions\/1565"}],"up":[{"embeddable":true,"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs\/121"}],"next":[{"title":"Failed to send request: A connection with the server could not be established","link":"https:\/\/www.versionsql.com\/help\/documentation\/error-messages\/failed-to-send-request-a-connection-with-the-server-could-not-be-established\/","href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs\/638"}],"prev":[{"title":"Expected FS format between '1' and '6'; found format '8'","link":"https:\/\/www.versionsql.com\/help\/documentation\/error-messages\/expected-fs-format-between-1-and-6-found-format-8\/","href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/docs\/1172"}],"wp:attachment":[{"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/media?parent=1454"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.versionsql.com\/help\/wp-json\/wp\/v2\/doc_tag?post=1454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}