No specific tips, other than to make sure everything is setup correctly including in Azure and your version of Service Desk is reasonably current.

https://www.novell.com/documentation/zenworks-service-desk-24.2/admin/data/b127s4i8.html#c000095

For Logs you can look here....

https://www.novell.com/documentation/zenworks-service-desk-24.2/service_desk_appliance/data/b1f5r5dv.html

I realize my post may not be that informational, but my guess there is just some small wrong OATH setting for O365 and azure

Craig Wilson said:

No specific tips, other than to make sure everything is setup correctly including in Azure and your version of Service Desk is reasonably current.

https://www.novell.com/documentation/zenworks-service-desk-24.2/admin/data/b127s4i8.html#c000095

For Logs you can look here....

https://www.novell.com/documentation/zenworks-service-desk-24.2/service_desk_appliance/data/b1f5r5dv.html

I realize my post may not be that informational, but my guess there is just some small wrong OATH setting for O365 and azure

Craig,

  Thanks for the response! I work with Justin and it really seems like maybe ZSD is "broken". We're using the latest version of ZSD with no available patches listed. 

  We are able to use PowerShell to authenticate using the same details we're entering into ZSD. In fact we're currently limping along by authenticating in PS and entering the access/refresh tokens into ZSD so that it can login and fetch emails.

The one bit of information that may be helpful is that the system was originally built with one name/ip and then moved into the name/ip that were used by our old system. I believe I updated the hostname and IP everywhere it is stored, but it's entirely possible I missed something somewhere.

I had a co-worker mention they had an issue that others could not replicate, but it appears the tokens expired is the ZSD server was off long enough and then had to use the ZSD Interfact to generate and use new tokens.

If you use the ZSD interface to regenerate tokens...does it start working?

www.novell.com/.../b127s4i8.html

Unfortunately, no, it simply displays the error(s) mentioned in the original post. We hoped once we generated by PowerShell we could plug them in then have it automatically update but it doesn't. 

On a side note, what exactly should be the formatting for Setup\Privileges\System\hostname? Is the above (domain redacted) correct? 

Hi Justin,

You have me Email....

Just send me unredacted details with pictures of the spots you want to know if the data is correct.

I have some folks looped in looking to see if we can figure out why you are getting that.

Whelp... we identified and added "log4j.logger.com.livetime.auth.OAuthTokenUtility=debug" to /opt/novell/servicedesk/server/webapps/LiveTime/WEB-INF/LiveTime.woa/Contents/Resources/logging.properties to log the OAuth process since there wasn't any details in the mail/message/EmailParser logs (mentioned in the cookbook). After doing so, we found "DEBUG117778[https-jsse-nio-443-exec-4] (OAuthTokenUtility.java:154) - Response code not ok from the provider. Response code is 401 " which lead us to discover copying the client secret into ZSD had formatting issues... 

We are now working fine after adjusting the client secret. 

Thanks for the Update!