Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with token auth #61

Open
LarryBarba opened this issue May 29, 2018 · 4 comments
Open

Issue with token auth #61

LarryBarba opened this issue May 29, 2018 · 4 comments

Comments

@LarryBarba
Copy link

I followed the instructions to integrate ZenDesk with VSTS but still keep coming up with an error .

image

Is it possible, I am just missing something simple? I have downloaded the latest 6.2 and per the instruction, I keep username blank and populate the password with the token I created in VSTS.

Please advise.

@LarryBarba LarryBarba changed the title Issue with tolken Issue with token auth May 29, 2018
@francisbachabi81
Copy link

I get the same. It used to work on this version but all of a sudden it stopped working. That was 5/24/2018 between 2PM and 3PM ET.
PAC for the User that we were previously using for this Integration (between Zendesk and VSTS) that I was originally using was setup to be authorized to all scopes. Also tried using Alternate Credentials but I get the same. Tried using PAC from a different Account with access to the Project and Same issue. I'm able to login to VSTS using both Accounts.

When I use Developer tools and Look at the Requests, I see below embedded in the Response:
Microsoft Internet Explorer's Enhanced Security Configuration is currently enabled on your environment. This enhanced level of security prevents our web integration experiences from displaying or performing correctly. To continue with your operation please disable this configuration or contact your administrator.

Error I get inside the Microsoft VSTS App for Zendesk: Ooops! Something went wrong while loading the app. Confirm that your Visual Studio Team Services alternate credentials are correct by clicking in the user icon.
When I use Developer tools, I see a Status Code = 203 Non-Authoritative Information.
From what I can tell, the HTTP 203 Non-Authoritative Information response status indicates that the request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy. In this case that could only be Zendesk since I'm able to authenticate properly when going directly to VSTS online And this used to work 5/24/2018 until about 2PM ET or 3PM ET.

Anyone else experiencing this same Issue?

@LarryBarba
Copy link
Author

LarryBarba commented May 29, 2018

I am trying it via Google Chrome and I get this error:
index.html:1 Uncaught (in promise) {readyState: 4, responseText: "DNS resolution error while resolving {_hiddenonpurpose_}", responseJSON: null, status: 502, statusText: "Bad Gateway"}readyState: 4responseJSON: nullresponseText: "DNS resolution error while resolving {_hiddenonpurpose_}"status: 502statusText: "Bad Gateway"__proto__: Object Promise.then (async) (anonymous) @ base_app.js:256 when @ base_app.js:252 _callee20$ @ app.js:1044 tryCatch @ runtime.js:65 invoke @ runtime.js:303 prototype.(anonymous function) @ runtime.js:117 step @ app.js:25 (anonymous) @ app.js:25 (anonymous) @ app.js:25 onAppActivated @ app.js:1081 _callee29$ @ app.js:1467 tryCatch @ runtime.js:65 invoke @ runtime.js:303 prototype.(anonymous function) @ runtime.js:117 step @ app.js:25 (anonymous) @ app.js:25 (anonymous) @ app.js:25 onLoginClick @ app.js:1488 dispatch @ [email protected](lodash.underscore.min.js),[email protected],[email protected],[email protected],[email protected]:73 r.handle @ [email protected](lodash.underscore.min.js),[email protected],[email protected],[email protected],[email protected]:73

@sotiriszegiannis
Copy link

Check out this little app i found this on the zendesk marketplace.
https://www.zendesk.com/apps/support/integratecloud-connector-for-vsts/?source=app_directory

@LarryBarba
Copy link
Author

hi @sotiriszegiannis ,

I did try that one a while back and was unsuccessful getting it to work.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants