search

krypted / jamf_zendesk

Plug-in to display Jamf items in the Zendesk sidebar.
MIT License
9 stars 1 forks source link

Pulling information #4

Open nicheledudley opened 5 years ago

nicheledudley commented 5 years ago

Hi-

I am getting the "Retrieving info from Jamf Pro...Please Wait!" notification. Is there an amount of time I should wait for this information to get pulled or is there an error log I can reference to see if I might have misconfigured something?

Thanks!

screen shot 2018-08-10 at 10 34 07 am
yuresko commented 5 years ago

Hello!

When it comes to zendesk apps, the tool is a sandboxed Java app/module. The console logs are only found in the web browser inspector/console dev tool. (Primarily for privacy and security reasons) If it’s taking a long time, you can open up “inspector” if you have chrome (or another browser inspector) and refresh the page, you should see the standard errors you would see if running the api calls manually. To access the console logs/errors in inspector, check out this resource: https://developers.google.com/web/tools/chrome-devtools/console/console-write. It may just be an invalid username and password base64, or sometimes an incorrect character in the url when first set up!

Please provide screenshots of inside the inspector if you still have trouble!

Jonathan

On Aug 10, 2018, at 10:34 AM, nicheledudley notifications@github.com wrote:

Hi-

I am getting the "Retrieving info from Jamf Pro...Please Wait!" notification. Is there an amount of time I should wait for this information to get pulled or is there an error log I can reference to see if I might have misconfigured something?

Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

nicheledudley commented 5 years ago

Thanks! That was helpful.

It looks like there is a problem with the proxy not being allowed. Is there anything that I need to do on the JSS Server side in oder to allow access?

yuresko commented 5 years ago

Hmm, you most likely shouldn't need to. Unless the JSS server itself is locked down and does not allow incoming traffic from Zendesk servers. There certainly may need to be some IP's whitelisted on the JSS to allow such incoming traffic, however when you ping a server that is behind a proxy you generally do not get any alerts that there is proxy causing the issue. Can you screenshot the full console and errors you're seeing and submit that in this so I can try to take a look? There are certainly many variables that could cause this, but I'm happy to try to help if I can.

On Fri, Aug 10, 2018 at 11:59 AM nicheledudley notifications@github.com wrote:

Thanks! That was helpful.

It looks like there is a problem with the proxy not being allowed. Is there anything that I need to do on the JSS Server side in oder to allow access?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/krypted/jamf_zendesk/issues/4#issuecomment-412127337, or mute the thread https://github.com/notifications/unsubscribe-auth/ANitSFQxYNkVz2TBytT7IkFHlHsJ-jGyks5uPa3MgaJpZM4V4TRS .

nicheledudley commented 5 years ago

Is this what you need? screen shot 2018-08-21 at 2 00 44 pm

yuresko commented 5 years ago

Apologies for the delay! Please ensure your domain, url and password are situated in the Zendesk -> App -> Manage -> Settings. Like the following:

domain*: company.jamfcloud.com

fullUrl*: https://company.jamfcloud.com

token*: dXNlcm5hbWU6cGFzc3dvcmQ=

Note that the "token" is base64 encoded as username:password.

chrisejbich commented 5 years ago

@yuresko We've also run into this issue. Attempted to get this setup during our JumpStart without success. Wondering if you found a solution. We've verified the above information a few times (domain, fullURL, token (in base64)) all to no success. I keep getting the same error as @nicheledudley. It appear to be a Proxy Error: Invalid Response, (please see the photo I've attached). Wondering if either of you found a fix to get this to work.

Screen Shot 2019-04-03 at 5 52 48 PM
yuresko commented 5 years ago

@chrisejbich @nicheledudley ...thanks for bringing this to my attention. Are you both using jamfcloud? Or are you hosting it yourselves?

chrisejbich commented 5 years ago

@yuresko. Good Question, I am using Jamfcloud, I am going to assume @nicheledudley is too.

chrisejbich commented 5 years ago

@yuresko any update on this being fixed for Jamf Cloud users? Alas it still doesn't work.

rani2001 commented 3 years ago

Hello,

Were you able to fix your problem because I have the same issue as you. I use Jamf Cloud. On the other hand, we use a DNS redirection with port 8443 which points to our company.jamfcloud.com instance. We did this so that we wouldn't have to re-enroll our computers when migrating from Jamf On Premise to Jamf Cloud.

Also, when you say "token", I'm not sure I understand. You must create a user in Jamf Cloud with all read access only and then encode the "user: password" created in base64. That's right ?

Thank you for your help

chrisejbich commented 3 years ago

@rani2001 I was not, we found a different workaround with third-party software. alas this was never officially resolved by jamf or @yuresko

rani2001 commented 3 years ago

Thank you for your reply @chrisejbich Never mind. However, can I ask you which tool you use instead?

Thank you

ryanmilliron commented 2 years ago

Just wanted to Follow up on this. I have the same Invalid Request when attempting to connect to a jamf cloud instance.