KNOWN ISSUE: Deployment Server authentication through the ASDK is not working
|Article:TECH28053|||||Created: 2007-03-28|||||Updated: 2007-07-23|||||Article URL http://www.symantec.com/docs/TECH28053|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
When role security is enabled in the DS console, any attempt to authenticate through the ASDK using C# code fails. The following error is returned:
An exception occoured
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Error: Could not authenticate Deployment Solution user. No credentials were provided for authentication. ---> Altiris.ASDK.ASDKException : Error: Could not authenticate Deployment Solution user. No credentials were provided for authentication.
Deployment Solution 6.8
Notification Server 6.0 SP3
This issue has been fixed in DS 6.8 SP2.
There appears to be several functions that are affected because of this bug. MoveComputerByGroupName and CreateJobScheduleByName are two known functions to be affected by this situation.
The work around is to use the CreateJobSchedule function as it is not affected by this particular problem. The following snippet of code can be helpful to show the implementation that should be used:
int scheduleID = scheduleManagment.CreateJobSchedule(computerID, jobID, false, "ASDK",
<start_time>9/12/2007 5:24:21 PM</start_time>
Console.WriteLine ("CreateJobSchedule complete" );
|Description||Logged in Littlebuggy (Altiris - Lindon, Plymouth) database|
Article URL http://www.symantec.com/docs/TECH28053