Identity Server and Ivanti Service Desk and Asset Central

Version 1

    Verified Product Versions

    Service Desk 2016.xAsset Manager 2016.xAsset Manager 2017.xService Desk 2017.x

    Identity Server has the following scope of usage :-

    1. Fully Qualified Domain Name use only
    2. Identity Server routes sessions to full \\servername\ FQDN addresses. Identity Server does not support use of public URL addresses (www.URL, http:URL) for accessing workspaces. If you require this do not use Identity Server for authentication
    3. Automatic new user creation
    4. Previously unknown users are always created automatically in the Servic desk database on first access through Identity Server
    5. Authentication support is currently limited to Active Directory only within corporate domain. No support is provided at this time for support through other authentication sources. Modification of Identity Service configuration files to support other sources (such as Google) is undertaken without Ivanti support.


    Xtraction with Workspaces and Service Desk

    Publishing Workspaces gadgets that display live Xtraction data requires the Workspaces instance to be configured to use Identity Server for authentication across both Service Desk and Xtraction. Consequently customers that wish to take advantage of the feature must also align with the above scope of usage



    Service Desk customer feedback has indicated that the functional scope of Identity Server limits some customer flexibility in authentication. Unless a Service desk customer has a requirement to use workspaces across both EndPointManager (previously LDMS) with Service Desk (previosuly LDSD), or to use Xtraction data in Workspace gadgets, the other authentication models are recommended for greater functional scope.


    We continue to seek feedback from support and customers on different usage profiles. Where customer need can be found only in Identity Server, please provide details to Product Management to help us with future product decisions, either by commenting on this thread or by emailing us at [email protected].