DLP API and Powershell

I need a solution

Hello all,

I am trying to hit the DLP API with the script below:

$Proxy = New-WebServiceProxy -Uri “https://<enforce Server>/ProtectManager/services/v2011/incidents?wsdl” -Credential domainuser

$type = $Proxy.GetType().Namespace

$incidentList = ($type + ‘.IncidentListRequest’)

$incidentListObj = New-Object ($incidentList)

$incidentListObj.savedReportId = ‘34309’

$incidentListObj.incidentCreationDateLaterThan = ‘2019-06-15T13:45:30’

$Proxy.incidentList($incidentListObj)

When I run that I get the following error:

Cannot convert argument “incidentListRequest”, with value:

“Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy13_services_v2011_incidents_wsdl.IncidentListRequest”, for “incidentList” to type

“Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy13_services_v2011_incidents_wsdl.IncidentListRequest”: “Cannot convert the

“Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy13_services_v2011_incidents_wsdl.IncidentListRequest” value of type

“Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy13_services_v2011_incidents_wsdl.IncidentListRequest” to type

“Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy13_services_v2011_incidents_wsdl.IncidentListRequest”.”

At C:UsersUserDocumentsDARReportsTestAPI2.ps1:12 char:1

+ $Proxy.incidentList($incidentListObj)

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [], MethodException

+ FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument

_______________________________________________________________________
I think I am close but not quite. Any tips or help would be greatly appreciated.

0

Related:

New Dell EMC ECS Software and Hardware Innovation Helps You Do More with Data

Object storage is quickly climbing its way to the top of the priority list for IT decision makers. For the uninitiated, object storage is an approach that addresses data storage as discrete units, called objects, and grants an application freedom to store an unlimited amount of data in a flat namespace versus a file hierarchy. Without getting too deep into the weeds, object-based solutions are one of the best ways to deal with endless data growth, at a price that won’t blow your budget out of the water. So, as data from applications, websites, video cameras, … READ MORE

Related:

CAS behavior for cross bucket access under same namespace is not supported in ECS-CAS

Article Number: 491848 Article Version: 2 Article Type: How To



ECS Appliance Hardware,ECS Appliance

CAS behavior for cross bucket access under same namespace is not supported in ECS-CAS. Centera supports this type of behavior. This is known limitation in ECS-CAS implementation and it comes from the architectural differences between Centera and ECS.

Description:

There are two CAS buckets under one namespace TEST.

dc_bucket

dr_bucket

There are two object users to have these buckets as default CAS bucket.

dc_profile has dc_bucket as default CAS bucket

dr_profile has dr_bucket as default CAS bucket

The below ACLs were configured.

dc_bucket: dc_profile -> Full, dr_profile -> Read & Read ACL

dr_bucket: dc_profile -> Read & Read ACL, dr_profile -> Full

After writing 1 object to ECS using dc_profile PEA, this clip can be accessed using dc_profile.However clip cannot be accessed using dr_profile and will end up with Error message was -10021 (CLIP_NOT_FOUND)

Related:

  • No Related Posts

Error 40020 (http: 409): Namespace conflict. Namespace shares a common mapping with another namespace

Article Number: 482255 Article Version: 4 Article Type: Break Fix



ECS Appliance Hardware,ECS Appliance Software with Encryption,ECS Appliance Software without Encryption,ECS DIY Software 2.2

You are trying to create a new namespace and you get this error:

“Error 40020 (http: 409): Namespace conflict. Namespace shares a common mapping with another namespace”

The issue is a User Admin can’t own more than one namespace. The problem is for ECS 2.2.0, if the User Admin is left blank, then the UI is finding a NULL User Admin matches any other namespace with a NULL User Admin and you will be faced with this error erroneously.

N/A

In ECS 2.2 a domain user can create a namespace and put themselves as the User Admin for this new namespace. If the same domain user then attempts to create a second namespace with the same User Admin, they will get the error above and this expected. Basically, one domain user can be the Admin User for only one namespace.

If a domain user is creating namespaces and leaving the Admin User blank, then this domain user ought to be able to create as many namespaces as he/she needs to create. However, there is a small defect in all ECS 2.2.0 versions where the NULL User Admin value is compared to the incoming NULL value from the subsequent namespace creation request. The user will receive the same error message. This small defect is resolved in ECS 2.2.1, which is also known as ECS 2.2 SP1.

Related:

Re: sudo file getting ovewritten

We have created a script that enables our ServiceDesk to close OPEN files on Isilon.

We did not want to use a root level account.

We created a custom Role=CloseSMB and gave it these privileges:

Console

Platform API

SSH

SMB

Namespace Traverse

Namespace Access

We created a local account called “Closer” and added it to our CloseSMB role.

The account could not run isi_for_array until we gave it some sudo rights and nopasswrd required

We added to sudo:

Closer ALL=(ALL) NOPASSWD: /usr/bin/isi_for_array, /usr/bin/isi

We added to all nodes in cluster.

The script worked.

I went in the GUI to check on CloseSMB privileges.

A few minutes later I was doing some more testing and the script failed.

Something took out our line:

Closer ALL=(ALL) NOPASSWD: /usr/bin/isi_for_array, /usr/bin/isi

How do we edit sudo and make it stick?

Elias

Related:

7021323: Web Services Target Namespace in Verastream Host Integrator

Default Values

The following table lists the default target namespace values by VHI product version:

VHI Version
Type
WSDL Default Target Namespace
7.5 SP1 or higher
(Any)
urn:xmlns:attachmate:vhi-ws:<model name>
7.0 – 7.5
Pooled
urn:xmlns:attachmate:vhi-ws:session:<pool name>
7.0 – 7.5
Non-pooled (model)
urn:xmlns:attachmate:vhi-ws:model:<model name>
6.6.189 – 6.6.222
.NET and Java
urn:xmlns:attachmate:vhi-wb-ws:<project name>
5.5 – 6.6.188
.NET
http://tempuri.org/
5.0 – 6.6.188
Java
http://<host name>:<port>/axis/services/<project name>

Customizing the Target Namespace

There are several methods available for modifying the namespace, depending on your product version.

Administrative Console

Beginning in version 7.5 SP1, you can set a custom target namespace prefix in Administrative Console (in Session Server Properties > Web Services). The model name gets appended to this prefix. Note: Beginning in version 7.7, this option is no longer recommended.

Beginning in version 7.7, you can view and set model- and pool-specific custom namespaces in Administrative Console (in Model Properties and Pool Properties respectively). Note: Values set in Administrative Console may be overwritten by subsequent model deployment.

Deployment Descriptor

Beginning in version 7.7, you can set a model- or pool-specific custom namespace in the model deployment descriptor (deploy_desc.xml file). In the <model-configuration> or <pool-configuration> node (just before the </model-configuration> or </pool-configuration> line), add the following:

<ws-config>

<ws-namespace>urn:xmlns:my-namespace</ws-namespace>

</ws-config>

where my-namespace is the desired custom target namespace.

For complete deployment descriptor XML examples, see http://docs2.attachmate.com/verastream/vhi/7.7/en/topic/com.attachmate.vhi.help/html/reference/deploy_descriptor.xhtml.

Modify plugin-cfg.xml File

In versions 7.5 SP1 through 7.6 SP1, to set a model- or pool-specific custom namespace, complete the following steps:

  1. Edit the plugin-cfg.xml file located in the %VHI_ROOT%/sesssrvr/services/ws/META-INF directory.
  2. Before the </properties> line, add one or more lines using the following syntax:
<entry key="model.model-name.namespace">urn:xmlns:my-namespace</entry>

-OR-

<entry key="session.pool-name.namespace">urn:xmlns:my-namespace</entry>

where model-name is the target model, or pool-name is the target pool, and my-namespace is the desired custom target namespace.

  1. After saving changes, restart the session server service as described in Technical Note 10004.

Legacy Web Service Projects

For web service Web Builder projects created in version 6.6 and earlier, and running in a later version, you can add or modify a targetnamespace=<value> line in the project.properties file.

Related:

  • No Related Posts

7021554: Errors in Microsoft Visual Studio When Using Verastream Host Integrator 7.x Web Service

The following errors or warnings may display when you add the Verastream Host Integrator (VHI) web service to your project, or subsequently attempt to build your project.

Warnings When Adding Service Reference

In your Microsoft Visual Studio 2008 or 2010 project using .NET Framework 3.0 or 3.5, after adding a service reference to the VHI web service WSDL, the Error List may display warnings similar to the following:

Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 2 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: lang' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 3 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: space' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 11 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: base' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 12 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: id' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 13 Column: 3

Validation Error: The attributeGroup 'http://www.w3.org/XML/1998/namespace:specialAttrs' has already been declared.



Custom tool warning: The optional WSDL extension element 'UsingAddressing' from namespace 'http://www.w3.org/2006/05/addressing/wsdl' was not handled.

XPath: //wsdl:definitions[@targetNamespace='urn:xmlns:attachmate:vhi-ws:<model or session>:<model name>']/wsdl:binding[@name='<model name>PortBinding']

Errors When Building Project in Visual Studio 2010

In a BizTalk Server 2010 project, after importing a VHI web service as a Service Reference and attempting to build the solution, the Error List may display multiple errors similar to the following:

Node "<Schema>" - Schema reference "http://<hostname>:9680/vhi-ws/<model or session>/<model name>/<file>.xsd" is not a valid reference or does not exist in the current project.

Figure 1. Sample build errors in Microsoft Visual Studio 2010 Error List

Errors When Building Project in Visual Studio 2008

When attempting to compile your project in Visual Studio, the Error List and build output may display multiple errors similar to the following:

error CS0102: The type '<project name>.<service reference name>.<type name>' already contains a definition for '<name>'

error CS0111: Type '<project name>.<service reference name>.<type name>' already defines a member called '<name>' with the same parameter types

Figure 2. Sample build errors in Microsoft Visual Studio 2008 Error List

Error in BizTalk WCF Service Consuming Wizard

If you are attempting to add a Verastream Host Integrator 7.0 web service WSDL to a Microsoft BizTalk Server 2006 R2 or 2009 project using the WCF Adapter, the BizTalk WCF Service Consuming Wizard may display the following error:

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Related:

Version 2.0.0 ToSpeech Method in UnitySDK

I have a product that has been running Watson SDK in Unity for several months and we imported the most recent version to our developer branch to integrate the new changes.

The first major conflict is found in TextToSpeech.ToSpeech() regarding the new generic Success and Fail Callback delegates.

TextToSpeech m_TextToSpeech = new TextToSpeech(_credentials);

RESTConnector.Error error = new RESTConnector.Error();

Dictionary customData = new Dictionary();

AudioClip newClip = new AudioClip();

string AI_Ouput = AIResponse.text;

m_TextToSpeech.ToSpeech(error, customData, AI_Ouput);

It requires 3 arguments: success, failure, and the string value. I am uncertain how to use these, and have tried building my own, but without luck. Am I overthinking the new implementation of ToSpeech() ?

I’m assuming I don’t need to manually build and declare these delegates since the namespace itself holds many different functions that build their own generic callbacks. The TextToSpeech class also requires Credentials, which I was never populating locally before.

Related:

  • No Related Posts