Jump to content

Osman

Hornbill Users
 View Profile  See their activity

  • Posts

    60

  • Joined

  • Last visited

 Content Type 

Posts posted by Osman

    Azure User Import failing on Scheduled Task

    in Integration Connectors, API & Webhooks

    Posted

    Spoke too soon, it worked once and hasn't since. I bit the bullet and completely recreated the Scheduled Task, it is still failing with the exact same error shown above, see latest below:

    2024/04/29 08:38:28 [MESSAGE] You're running the latest version of this utility: 4.2.1
    2024/04/29 08:38:28 [ERROR] Error processing authentication: Decryption of authentication data failed: Key not valid for use in specified state.

    The import still runs without issue from the Command Prompt, any ideas?

    Azure User Import failing on Scheduled Task

    in Integration Connectors, API & Webhooks

    Posted

    Looks like I am back to square one, the underlying cause of the error on my last post was that there were missing rules in the API Key. I am still getting the following error:

    2024/03/18 09:05:16 [WARN] Current version 4.2.0 (patch) is greater than or equal to the latest release version on Github 4.2.0
    2024/03/18 09:05:16 [ERROR] Error processing authentication: Decryption of authentication data failed: Key not valid for use in specified state.

    Having been through the Azure Import documentation again, there is a suggestion that the executable should be in the profile folder of the user that undertook the first run, tested this on the offchance that it would make a difference, still getting the error above.

    I still don't understand how running from the command line works without issue, but fails as part of a Scheduled Task.

    Azure User Import failing on Scheduled Task

    in Integration Connectors, API & Webhooks

    Posted

    Hi Steve,

    But neither of the conditions in the Documentation:

    • When the user who runs the import is not the same user who first ran the import;
    • When the import is run on a different computer from the one that originally performed the authentication details encryption.

    Is true in my case, as I have stated at least twice already. It is the same device and using the same user that originally processed it. Also, this does not explain why running the import manually using the command prompt works?

    Anyway, I will do as suggested. We have three other imports that are also run for other types of user, what impact will it have on those, as they are all running through a schedules task?

    Thanks

    Osman

    Azure User Import failing on Scheduled Task

    in Integration Connectors, API & Webhooks

    Posted

    Hi Steve,

    Which scenario, do you mean:

    Quote

    The authentication details (Instance ID & API Key) is stored in the import.cfg file that is created/stored with the .exe.

    Only the WINDOWS account which CREATED the import.cfg has access to the details it contains!

    IF you are running the .exe in YOUR account and all works, then that would explain why the Service Account can't get the info out.

    Use "Run As..." or "runas" with the service account to set up the import.cfg which the Service Account will use (under the Task Scheduler)

    That was from SamS' response of the 7th Feb?

    If so, I already clarified that both the Scheduled Task and the manual execution of the import are being performed by the exact same account.

    Thanks

    Osman

    Azure User Import failing on Scheduled Task

    in Integration Connectors, API & Webhooks

    Posted

    Afternoon All,

    A bit of a weird one. The Azure Import for users has been working happily for some time now. However, over the last month or two the process is falling on the Scheduled Task and the content of the log file is:

    2024/02/07 14:08:15 [MESSAGE] ---- Azure Import Utility v4.1.1 ----
    2024/02/07 14:08:15 [MESSAGE] Flag - config goAzure2HUserImport
    2024/02/07 14:08:15 [MESSAGE] Flag - logprefix 
    2024/02/07 14:08:15 [MESSAGE] Flag - dryrun false
    2024/02/07 14:08:15 [MESSAGE] Flag - instanceid 
    2024/02/07 14:08:15 [MESSAGE] Flag - apitimeout 60
    2024/02/07 14:08:15 [MESSAGE] Flag - workers 1

    2024/02/07 14:08:15 [MESSAGE] Flag - forcerun true
    2024/02/07 14:08:15 [WARN] Current version 4.1.1 (patch) is greater than the latest release version on Github 4.2.0
    2024/02/07 14:08:15 [MESSAGE] Loading KeySafe Authentication Data: 13

    However, if I run this directly from the command line, which in essence is exactly the same thing, it works without issue. Any ideas?

    Thanks

    Osman

    Email Back Button - Missing

    in Collaboration

    Posted

    Hi Steve,

    Within a Incident or Service Request, under the Details node, there is the option at the bottom to preview the generating email. There used to be, on a previous instance of the UI, a Back button to return to the ticket, this seems to have dissapeared.

    Thanks

    Osman

    SSO Question

    in System Administration

    Posted

    Hi Gerry,

    I am not sure that I would say bypass it altogether, I am thinking more that we would have either:

    - A url that uses SSO without choice of direct login that we would be able to publish internally;

    - The sign in page has a detection method that can see that the browser is signed in with a valid SSO account and sign straight in without displaying the options. We have other SAAS systems that are capable of doing this, our room booking system for example.

    Thanks

    Osman

    SSO Question

    in System Administration

    Posted

    Morning All,

    I am reasonably certain that this has been asked for before, I just can't find it in the community. When we access our SSO url, in a browser that has an active, signed in session, we are always presented with the Single Sign-On/Direct Login options. Is there any way to adjust this so that the system detects the signed in status of the browser and immediately provides access? This is more of an issue for Basic users accessing the portal. 

    Thanks

    Osman

    Archived User not showing in User list

    in Service Manager

    Posted

    Morning All,

    This is a bit weird. I have been advised that a User has not able to access the self-service portal. I have checked the sync log and can see that there are the following entries:

    2023/11/02 03:02:58 [DEBUG] Azure User ID: '{UserID}' NOT Found

    2023/11/02 03:02:59 [DEBUG] User Create: {UserID} ({UserID})
    2023/11/02 03:02:59 [ERROR] Unable to Create User: {UserID} Error: User already exists with account status: archived

    I have checked the database, user doesn't exist. I have manually eyeballed the user list, user doesn't exist. I have attempted to manually re-add the user, and get an error that the user exists in an Archived state.

    Any advice would be welcomed as to how I can re-activate the user?

    Thanks

    Osman

    IT Only Self-Service Portal

    in Service Manager

    Posted

    Hi All,

    With other ITSM's I have been lucky enough to administer there have been methods by which I was able to allow the Service Desk to create quick tickets for regular requests and incidents. I believe I can do the same simply by creating Workflows that pre-populate specific fields. What I would like to know is whether it is possible to publish these quick tickets in a Service Desk, or IT only area? Ideally, I would like a Portal similar to the user facing Self-Service portal but with the previously mentioned quick tickets linked. On the face to it, the only way I can think of to achieve this would be to create a new Service in the Service Portfolio and limit it to the IT Teams that would use it and then add the Quick Ticket workflows to that Service.

    Any other suggestion/ideas?

    Thanks

    Osman

×
×
  • Create New...