Jordan Gooding-McGovern

Hi @Llyr is there anything output in the console output/debug logs tabs? They should be a good starting point to find out more.

Hi Bill, Nothing in the config file seems incorrect. Normally the log should have more information including a link to download the report. Could you confirm if there's any more information in the log file and if so paste it in with any potentially sensitive data removed. Is the "reports" folder being populated with any data? Jordan

Hi @Sam P Thanks for information you've provided! I've just pushed a change live which has updated the descriptions and should have resolved the error you've shown above. Do let me know if you run into any other problems. Jordan

There's a chance that it didn't automatically update your hornbill AD package and thus the changes haven't come through yet (this too will be fixed in the next release) if this has happened, please uninstall + reinstall the Hornbill Active Directory User Management package and it should then work.

Hey @Sam P, this was added in our latest ITOM update: https://community.hornbill.com/topic/27940-new-update-itom-packages-149/#comment-128551 but I can see that the description wasn't updated to reflect that. If you type in 'never' for the expiration date, it will be set to 'never' in AD. A change to update the description is currently working its way through our developer pipeline (along with some other small changes) and should be in the next release. Do let us know if you run into any problems. Jordan

@Berto2002 I've added it to our internal list as an integration request but if you do send it through as an integration request on the forum, I'll update the internal list with any additional info.

Hi Berto, At present we don't have a feature built into Hornbill which will set a users Out of Office state in O365. But I can see why this would be a useful feature. After some preliminary investigation I can see this https://learn.microsoft.com/en-us/graph/api/user-update-mailboxsettings?view=graph-rest-1.0&tabs=http graph API exists and should allow us to achieve what you want. We'll look into getting this one added for you.

@dmonteleone We've made a change to the logic in the backend which will fix tokens expiring before the 90 day default - please let me know if you continue running into issues.

Hi @Berto2002, quick update, the docs have been updated now to show the deprecated status of the tool and the github repository archived.

Hi Dan, When run with -creds=true that will check to see whether or not the API Key has been entered correctly. For the first run, you'll want to run it without the extra flag. When you first run the exporter without that flag. It should then prompt you to enter the API key and instance ID. You should also notice an "export.cfg" file being created. Afterwards if you run it with -creds=true it will only output the stored APIKey. The error "Could not decrypt authentication details" leads me to assume the export.cfg file hasn't been created yet. I'll look into updating our documentation to make things clearer as I can see it's missing that flag Jordan

Hi @dmonteleone Do you have any timeframes for the credentials expiring? (E.g. a day, a week, a month ,3-6months) That will help us investigate further on our end and see if/where things could be tripping up. I remember reading in the MS documentation a while ago that refresh tokens only last 90 days of inactivity, it was a security change I believe.

Hi @davidrb84 I'm just about to investigate this one, as I do so could you try a few amendments to creds page: oAuth Scope: signature extended access URL: https://account-d.docusign.com/oauth/token Additional Params: prompt=login Refresh Body: grant_type=&[credentials.oauth_refresh_grant_type]&refresh_token=&[credentials.oauth_refresh_token] You may also have a different API endpoint (though the one you have entered should work for testing purposes) Do let me know if this has helped.

@Gareth Cantrell Another iBridge release has just hit live which should resolve the problems you're facing in this thread. Do let me know if there's anything amiss!

@Gareth Cantrell Once again I appreciate the detailed response and troubleshooting on your end, I'll review it and let you know once there's an update!

@Gareth Cantrell The latest iBridge release contains the changes asked for in this thread. I've added an optional field in the post message method which allows users to reply via the method and have fixed the bug causing the TS to fail to be returned. The old reply method has been left in, in case users have that already cemented into their workflows.