Address parameters in the signature definitions (4.1)

Is there any way to change the action triggered by the signature based upon the network/host source/destination address in all kinds of engines? In Atomic engine it is possible - for example triggering different levels of alarms, based upon the victim network address. What about the all other engines?

Question: Is there any way to change the action triggered by the signature based upon the network/host source/destination address in all kinds of engines?
Response: No. When the signature is defined the selected actions will take place regardless of the addresses (unless the alarm is filtered).
Question: In Atomic engine it is possible - for example triggering different levels of alarms, based upon the victim network address. What about the all other engines?
Answer: No In version 4.x the alarm is either triggered and the actions taken, or the alarm is filtered and no actions are taken.
SIDE NOTE:
Some of this changes in version 5.0.
You still won't be able to assign specific actions for a given address set. But combinations of some of the added features may come close to providing you the granularity you are asking for.
I would suggest posting this question again after 5.0 is released. Then I will be able to go into feature details and give you some hints and tricks to get close to what you are asking for.

Similar Messages

How to make input parameters as optional in the function definition

I have created a function for a data service which is at the Normalized layer and has 3 input parameters.
This function is called at the Integration layer in which we have to pass only one parameter. But for the remaning 2 parameters it is throwing an error as we cannot pass those parameters.
Is it possible that we can pass less number of parameters in the higher layer.
I had also made those parameters as optional in the function definition(by applying '?' while defining the arguments-e.g. $x as xs:string?), but error was thrown while generating the query plan.
I have attached a Demo project, in which i have defined a function at the normalized layer and this function is been called at the integration layer.
Thanks,
Kinjal

Thanks mreiche for the reply
But the problem is that while writing
function myfunction( arg1 as xs:string, $arg2 as xs:string?) { ... }
in function definition in the normalized layer, the query plan is throwing following error:-
com.bea.ld.QueryException: Cannot generate XQuery for the function {ld:DemoProject/Normalized/TestGeo}getGeo:3
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:248) at com.bea.ld.Server_ydm4ie_EOImpl_816_WLStub.executeFunction(Unknown Source) at workshop.liquiddata.xds.views.queryplan.QueryPlanPanel.compileFunction(QueryPlanPanel.java:583) at workshop.liquiddata.xds.views.queryplan.QueryPlanPanel.access$900(QueryPlanPanel.java:39) at workshop.liquiddata.xds.views.queryplan.QueryPlanPanel$5.run(QueryPlanPanel.java:469) at java.lang.Thread.run(Thread.java:534)
Caused by: com.bea.ld.QueryException: Cannot generate XQuery for the function {ld:DemoProject/Normalized/TestGeo}getGeo:3 at com.bea.ld.EJBRequestHandler.invokeFunction(EJBRequestHandler.java:720) at com.bea.ld.EJBRequestHandler.executeFunction(EJBRequestHandler.java:339) at com.bea.ld.ServerBean.executeFunction(ServerBean.java:95) at com.bea.ld.Server_ydm4ie_EOImpl.executeFunction(Server_ydm4ie_EOImpl.java:312)
at com.bea.ld.Server_ydm4ie_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:120)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: com.bea.ld.server.FunctionCallQueryBuilder$QueryBuilderException: The following parameter type is not supported: {http://www.w3.org/2001/XMLSchema}string?
at com.bea.ld.server.FunctionCallQueryBuilder.addParameter(FunctionCallQueryBuilder.java:257)
at com.bea.ld.server.FunctionCallQueryBuilder.buildQuery(FunctionCallQueryBuilder.java:99)
at com.bea.ld.EJBRequestHandler.invokeFunction(EJBRequestHandler.java:716)
But no error is thrown when I call this function at the Integration layer,using
for $f in mfunction( 'test', () )
and the output which i get is as expected.

I have just upgraded to Mountain Lion and my signatures for my Mail is not showing up. I have the signatures inthe preference panes and selected for the email address, but when I make a new message, the signature shows as none and doesn't give me a choice

I have just upgraded to Mountain Lion and my signatures for my Mail are not showing up. I have the signatures inthe preference panes and selected for the email address, but when I make a new message, the signature shows as none and doesn't give me a choice. Yesterday, the signatures were stacking instead of switching to the one I wanted to choose.

I had this and fixed it.
I had upgraded to Mountain Lion and my signatures in Mail were fine. But then about a week later, I got a new computer and used Migration Assistant to copy my stuff to the new machine. Upon opening Mail, I had all the correct Signature information in the Preferences>Signatures window, but nothing worked.
After lots of hunting, I found the Signature Folder. It's in:
Yourusername>Library>Mail>V2>MailData>Signatures
Looking at my previous setup (which works) I saw in that folder two types of files: .webarchive and .siganture
Looking in my new machine's Signature folder, I saw only the .webarchive folders, not the .signature folders
Since this was literally a clone of my previous setup to a new machine, here's what I did:
1. Quit Mail
2. In Problem machine, go to
Yourusername>Library>Mail>V2>MailData>Signatures
3. Move the Signatures folder someplace safe, but out of the MailData folder
4. Get the Signatures Folder from the working install (like a backup) and copy it to the MailData folder on the problematic machine
5. Start Mail on the problem machine
This worked for me. I don't know why Migration Assistant didn't copy the full signature folder, but this fixed it. It worked perfectly partly because I had just backed up with Carbon Copy Cloner and the very next day set up the new machine. I don't know where Lion or earlier versions of mail stored signatures, but the absence of the .signature filetype seems to be the problem.
Hope this helps

Why does Signature with an email address appear on the top left hand corner of each template? Is there a way to remove this or is it standard? Thank you!

I'm not sure this is necessary or is it proof to the customer of where the proof/invoice is coming from for approval?
Thank you for your time and consideration!

Hi Brandon,
By default, if you are not placing the signature field in document manually, a signature block ( having signature and email address ) is placed at the bottom left corner of document by default.
While sending the document from Send tab, just check "Preview, Position Signatures or add form fields" and hit Next. In Preview page, you can drag and drop Signature field along with other form fields at appropriate position in document.
Here is the link for reference:
http://helpx.adobe.com/echosign/kb/hub7.html
Let me know if you need more help.
Regards,
-Rijul

CreateAuthenticatedSessionToken: The signature of the request does not match the request parameters

I'm creating an app using the SODA Architecture.
I could successfully create an app and make the client to authorize it.
Result of newApplicationCreationInfo:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>
<code>0</code>
</status>
<wc:info xmlns:wc="urn:com.microsoft.wc.methods.response.NewApplicationCreationInfo">
<app-id>4417587e-46d1-49ee-a0fa-50dbfdcf932c</app-id>
<shared-secret>gBksYDAqcuAUXK+zyvfFW9F0sy8nchwnplJ6K7aKmAM=</shared-secret>
<app-token>AiAAANDl....A5b9fxVIlXEloouci6jGhY/A==</app-token>
</wc:info>
</response>
I'm using the app-token to build the redirect url, and I get to authorize the new app.
then, using the new child app id and the shared-secret I built the
CreateAuthenticatedSessionToken:
<?xml version="1.0" encoding="UTF-8"?>
<wc-request:request xmlns:wc-request="urn:com.microsoft.wc.request">
<header>
<method>CreateAuthenticatedSessionToken</method>
<method-version>2</method-version>
<app-id>4417587e-46d1-49ee-a0fa-50dbfdcf932c</app-id>
<language>en</language>
<country>US</country>
<msg-time>2013-01-01T00:00:00Z</msg-time>
<msg-ttl>1800</msg-ttl>
<version>2.0.0.0</version>
</header>
<info>
<auth-info>
<app-id>4417587e-46d1-49ee-a0fa-50dbfdcf932c</app-id>
<credential>
<appserver2>
<hmacSig algName="HMACSHA256">PcW4f9krD1O43O4JGBGEkqDlpatFIUUQY9JejHji0XA=</hmacSig>
<content>
<app-id>4417587e-46d1-49ee-a0fa-50dbfdcf932c</app-id>
<hmac>HMACSHA256</hmac>
<signing-time>2013-12-17T14:19:58.623Z</signing-time>
</content>
</appserver2>
</credential>
</auth-info>
</info>
</wc-request:request>
Being hmacSig value the encryption of "<content>....</content>" using shared-secret value as private key:
hmacSig = Encodingutil.base64Encode(Crypto.generateMac('hmacSHA256', Blob.valueOf(body), Blob.valueOf(sharedSecret)))
this returns an error code 11: The signature of the request does not match the request parameters.
I'm using the following endpoint: https://platform.healthvault-ppe.com/platform/wildcat.ashx
Also the redirection url I received after authorizing the app contains the following:
https://<MY_URL>/?gws_rd=cr&ei=h5ewUuKLJa7IsASc4YHIAw I'm not using this parameters, if that helps.
Any hint will be greatly appreciated.
UPDATE: I already checked the HMAC encoding using a third party service and it returned the same as my app

I figured this out (God bless Pair Programming):
I was signing incorrectly:
On the newApplicationCreationInfo:
My Shared Secret is : gBksYDAqcuAUXK+zyvfFW9F0sy8nchwnplJ6K7aKmAM=
But BEFORE hashing the "<content>...</content>" i need to decode my secret that is:
hmacsig = calculateHMAC256(content, sharedSecret.decodeBase64())

Unrecognized Lync contact opens when sip address added in the outlook signature block

I have added my sip address into my outlook signature block. Why does an inactive contact conversation opens, if I click on the link in the signature? It looks, like my profile in Lync, with the same picture and name, but the presence cannot be recognized,
thus a Lync message cannot be sent.

Hi,
Which Lync 2010 command-line parameter did you added in the signature block?
If you want to open the IM conversation windows of you when others clicking the signature, you can use the following command-line parameter:
Sip:[email protected]
Sips:[email protected]
Im:<sip:[email protected]>
More details:
https://technet.microsoft.com/en-us/library/gg398376(v=ocs.14).aspx
If you enter the correct command-line, however the issue persists, please try to delete your Lync user profile with the following path and then test the issue again:
HKCU\Software\Microsoft\Communicator\[email protected]
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

AXIS - The arguments do not match the signature

I have developed a web service and deployed it, everything looks fine, but it doesn't work. When I try to call the method I get an exception:
Tried to invoke method public static dk.decon.dsi.midtier.dto.DsiTO dk.decon.dsi.facade.DataFacade.getJournal(int) throws dk.decon.dsi.midtier.exceptions.DaoException with arguments null. The arguments do not match the signature.; nested exception is: java.lang.IllegalArgumentException
I think that the problem is that I'm calling a method that returns a complex object, apparently AXIS is having problems with those?
The wsdl looks like:
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="urn:DataFacadeWS" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:DataFacadeWS" xmlns:intf="urn:DataFacadeWS" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://dto.midtier.dsi.decon.dk" xmlns:tns2="http://exceptions.midtier.dsi.decon.dk" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- 
- <wsdl:types>
- <schema targetNamespace="http://dto.midtier.dsi.decon.dk" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://exceptions.midtier.dsi.decon.dk" />
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
- <complexType name="Address">
- <sequence>
<element name="addressNumber" type="xsd:int" />
<element name="addressType" nillable="true" type="xsd:base64Binary" />
<element name="city" nillable="true" type="soapenc:string" />
<element name="country" type="xsd:int" />
<element name="faxNumber" nillable="true" type="soapenc:string" />
<element name="journalNumber" type="xsd:int" />
<element name="poboxnumber" nillable="true" type="soapenc:string" />
<element name="postalCode" nillable="true" type="soapenc:string" />
<element name="streetName" nillable="true" type="soapenc:string" />
<element name="streetNumber" nillable="true" type="soapenc:string" />
<element name="telephoneNumber" nillable="true" type="soapenc:string" />
</sequence>
</complexType>
- <complexType name="Detachment">
- <sequence>
<element name="accept" type="xsd:short" />
<element name="companyID" type="xsd:int" />
<element name="contactPerson" nillable="true" type="soapenc:string" />
<element name="contractDate" nillable="true" type="xsd:dateTime" />
<element name="contractSuspended" type="xsd:short" />
<element name="country" type="xsd:int" />
<element name="definedByCompanyID" type="xsd:short" />
<element name="department" nillable="true" type="soapenc:string" />
<element name="description" nillable="true" type="soapenc:string" />
<element name="detachEmployer" type="xsd:short" />
<element name="detachmentID" type="xsd:int" />
<element name="employerAgencyID" type="xsd:short" />
<element name="endDate" nillable="true" type="xsd:dateTime" />
<element name="fullTime" type="xsd:short" />
<element name="function" nillable="true" type="soapenc:string" />
<element name="hireFireByCompanyID" type="xsd:short" />
<element name="homeEmployer" type="xsd:short" />
<element name="initiativeCompanyID" type="xsd:short" />
<element name="journalNumber" type="xsd:int" />
<element name="layOffPaymentByCompanyID" type="xsd:short" />
<element name="lineOfBusiness" nillable="true" type="soapenc:string" />
<element name="nativeStatus" type="xsd:short" />
<element name="occupation" nillable="true" type="soapenc:string" />
<element name="occupationContent" nillable="true" type="soapenc:string" />
<element name="otherCompany" type="xsd:short" />
<element name="personID" type="xsd:int" />
<element name="salaryByCompanyID" type="xsd:short" />
<element name="salaryRaiseByCompanyID" type="xsd:short" />
<element name="socialSecurityByCompanyID" type="xsd:short" />
<element name="startDate" nillable="true" type="xsd:dateTime" />
<element name="workstationID" type="xsd:int" />
<element name="workstationIDNull" type="xsd:boolean" />
</sequence>
</complexType>
- <complexType name="Homeaddressconnect">
- <sequence>
<element name="addressNumber" type="xsd:int" />
<element name="addressType" nillable="true" type="soapenc:string" />
<element name="fromDate" nillable="true" type="xsd:dateTime" />
<element name="personId" type="xsd:int" />
<element name="toDate" nillable="true" type="xsd:dateTime" />
</sequence>
</complexType>
- <complexType name="Journal">
- <sequence>
<element name="journalNumber" type="xsd:int" />
</sequence>
</complexType>
- <complexType name="Person">
- <sequence>
<element name="birthDate" nillable="true" type="xsd:dateTime" />
<element name="birthName" nillable="true" type="soapenc:string" />
<element name="cellPhoneNumber" nillable="true" type="soapenc:string" />
<element name="country" type="xsd:int" />
<element name="familyName" nillable="true" type="soapenc:string" />
<element name="firstNames" nillable="true" type="soapenc:string" />
<element name="homeAddressNumber" type="xsd:int" />
<element name="journalNumber" type="xsd:int" />
<element name="occupationStatus" nillable="true" type="xsd:base64Binary" />
<element name="personID" type="xsd:int" />
<element name="personalEmail" nillable="true" type="soapenc:string" />
<element name="professionalEmail" nillable="true" type="soapenc:string" />
<element name="socialSecurityDate" nillable="true" type="xsd:dateTime" />
<element name="socialSecurityNumber" nillable="true" type="soapenc:string" />
</sequence>
</complexType>
- <complexType name="EmployeeTO">
- <sequence>
<element name="address" nillable="true" type="tns1:Address" />
<element name="detachment" nillable="true" type="tns1:Detachment" />
<element name="homeaddressconnect" nillable="true" type="tns1:Homeaddressconnect" />
<element name="journal" nillable="true" type="tns1:Journal" />
<element name="person" nillable="true" type="tns1:Person" />
</sequence>
</complexType>
- <complexType name="Company">
- <sequence>
<element name="companyAddressNumber" nillable="true" type="soapenc:string" />
<element name="companyID" type="xsd:int" />
<element name="companyName" nillable="true" type="soapenc:string" />
<element name="companyRegistrationNumber" nillable="true" type="soapenc:string" />
<element name="country" type="xsd:int" />
<element name="journalNumber" type="xsd:int" />
</sequence>
</complexType>
- <complexType name="Homeemployment">
- <sequence>
<element name="companyID" type="xsd:int" />
<element name="contract" type="xsd:short" />
<element name="contractDate" nillable="true" type="xsd:dateTime" />
<element name="country" type="xsd:int" />
<element name="detachmentLetter" type="xsd:short" />
<element name="endDate" nillable="true" type="xsd:dateTime" />
<element name="homeEmploymentID" type="xsd:int" />
<element name="personID" type="xsd:int" />
<element name="startDate" nillable="true" type="xsd:dateTime" />
</sequence>
</complexType>
- <complexType name="EmployerTO">
- <sequence>
<element name="address" nillable="true" type="tns1:Address" />
<element name="company" nillable="true" type="tns1:Company" />
<element name="detachment" nillable="true" type="tns1:Detachment" />
<element name="homeemployment" nillable="true" type="tns1:Homeemployment" />
<element name="person" nillable="true" type="tns1:Person" />
</sequence>
</complexType>
- <complexType name="HistoryTO">
- <sequence>
<element name="detachment" nillable="true" type="tns1:Detachment" />
</sequence>
</complexType>
- <complexType name="OccupationTO">
- <sequence>
<element maxOccurs="unbounded" name="address" nillable="true" type="tns1:Address" />
<element name="company" nillable="true" type="tns1:Company" />
<element name="detachment" nillable="true" type="tns1:Detachment" />
</sequence>
</complexType>
- <complexType name="QuestionsTO">
- <sequence>
<element name="address" nillable="true" type="tns1:Address" />
<element name="company" nillable="true" type="tns1:Company" />
<element name="detachment" nillable="true" type="tns1:Detachment" />
<element name="person" nillable="true" type="tns1:Person" />
</sequence>
</complexType>
- <complexType name="WorkplaceInfoTO">
- <sequence>
<element name="address" nillable="true" type="tns1:Address" />
<element name="company" nillable="true" type="tns1:Company" />
<element name="detachment" nillable="true" type="tns1:Detachment" />
</sequence>
</complexType>
- <complexType name="DsiTO">
- <sequence>
<element name="employeeTO" nillable="true" type="tns1:EmployeeTO" />
<element name="employerTO" nillable="true" type="tns1:EmployerTO" />
<element name="historyTO" nillable="true" type="tns1:HistoryTO" />
<element name="journalNo" type="xsd:int" />
<element name="occupationTO" nillable="true" type="tns1:OccupationTO" />
<element name="questionsTO" nillable="true" type="tns1:QuestionsTO" />
<element name="workplaceInfoTO" nillable="true" type="tns1:WorkplaceInfoTO" />
</sequence>
</complexType>
</schema>
- <schema targetNamespace="http://exceptions.midtier.dsi.decon.dk" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://dto.midtier.dsi.decon.dk" />
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
- <complexType name="DaoException">
- <sequence>
<element name="cause" nillable="true" type="xsd:anyType" />
</sequence>
</complexType>
</schema>
</wsdl:types>
- <wsdl:message name="saveRequest">
<wsdl:part name="dsiTO" type="tns1:DsiTO" />
</wsdl:message>
- <wsdl:message name="getJournalResponse">
<wsdl:part name="getJournalReturn" type="tns1:DsiTO" />
</wsdl:message>
- <wsdl:message name="saveResponse">
<wsdl:part name="saveReturn" type="tns1:DsiTO" />
</wsdl:message>
- <wsdl:message name="getJournalRequest">
<wsdl:part name="journalNo" type="xsd:int" />
</wsdl:message>
- <wsdl:message name="DaoException">
<wsdl:part name="fault" type="tns2:DaoException" />
</wsdl:message>
- <wsdl:portType name="DataFacade">
- <wsdl:operation name="getJournal" parameterOrder="journalNo">
<wsdl:input message="impl:getJournalRequest" name="getJournalRequest" />
<wsdl:output message="impl:getJournalResponse" name="getJournalResponse" />
<wsdl:fault message="impl:DaoException" name="DaoException" />
</wsdl:operation>
- <wsdl:operation name="save" parameterOrder="dsiTO">
<wsdl:input message="impl:saveRequest" name="saveRequest" />
<wsdl:output message="impl:saveResponse" name="saveResponse" />
<wsdl:fault message="impl:DaoException" name="DaoException" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="DataFacadeSoapBinding" type="impl:DataFacade">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="getJournal">
<wsdlsoap:operation soapAction="" />
- <wsdl:input name="getJournalRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DataFacadeWS" use="encoded" />
</wsdl:input>
- <wsdl:output name="getJournalResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DataFacadeWS" use="encoded" />
</wsdl:output>
- <wsdl:fault name="DaoException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="DaoException" namespace="urn:DataFacadeWS" use="encoded" />
</wsdl:fault>
</wsdl:operation>
- <wsdl:operation name="save">
<wsdlsoap:operation soapAction="" />
+ <wsdl:input name="saveRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DataFacadeWS" use="encoded" />
</wsdl:input>
- <wsdl:output name="saveResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DataFacadeWS" use="encoded" />
</wsdl:output>
- <wsdl:fault name="DaoException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="DaoException" namespace="urn:DataFacadeWS" use="encoded" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="DataFacadeService">
- <wsdl:port binding="impl:DataFacadeSoapBinding" name="DataFacade">
<wsdlsoap:address location="http://localhost:8080/axis/services/DataFacade" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Any help will be greatly appreciated....

Hi,
That sounds interesting.
I tried a small example which calls a Sequence which passes two paramaters, one number and one string. I then linked these two locals except I specified them as one string and one number. I changed the load setting of the SequenceCall Step to Preload when sequencefile opened. I saved and closed the file.
When I opened the file, no warning or error was flagged. When the Sequence was run it errored on the call to the step with "Type of argument expression 'Locals.arg1' is incompatible with parameter 'Arg1'. Expected Number, found String".
It would be quite envolved to a find all the sequences in a file, get it's arguments, get the Expression, check if its not a constant and if not get the type of the variable in the expression and check it against argument parmater type. Repeat this for all parameter arguments. Repeat this for all sequences.
Then how do you report an errors. How do you handle SequenceCalls that call sequences contained in different sequencefiles.
You can find the arguments in the Step.TS.SData.ActualArgs.
Regards
Ray Farmer
Regards
Ray Farmer

Populating the Signature field of OIM UPA table

The OIM UPA table has a SIGNATURE field which customers can use for storing digital signature of the snapshot (for non-repudiation purposes).
By default - the value of this field is "NULL" in the database.
Did not find any documentation on how this field is populated.
Has any one made use of this non-repudiation feature.
Thanks,
Chetan

If you want this functionality it is actually not that hard to create a scheduled task that populates the signature field using a third party non repudiation provider.
Doing local non repudiation is per definition non useful so you do need a trusted third party (i.e. Guardtime (http://www.guardtime.com/)) that provides the service.
Best regards
/Martin

How do I clone my computer's MAC address on to the AE base station?

This is just driving me nuts. I've looked at responses to this question on the internet, and it appears that the Airport Extreme Base Station can't perform a function that nearly all WAN home routers have been able to perform for a decade: "cloning" a MAC Address. My internet provider uses the MAC address of one of my computers to identify a valid connection, and my old Belkin router just cloned the computer's MAC address. If the AEBS can't do that then it's a rather serious design flaw, and if I'd known that I'd never have bought the device. I noticed that there's something called a "Client ID" so I input my computer's MAC Address for that, but the Base Station still can't connect to the internet.
I don't want to have my ISP reset my valid MAC address (even if they could, which isn't clear to me) because I may need to connect to the internet directly in the event of problems... say the Base Station malfunctions.
I bought the base station so that I could connect peripherals to it, but if it can't connect to the internet that renders it practically useless.
Are there any workarounds? Anyone have any ideas?

I can see that no one is bothering to respond to this question, so I thought I'd post a resolution. I don't know if one can alter the ID of the AE Base by cloning a computer's MAC address. The next best thing would be to easily alter the MAC address that the ISP identifies as legitimate. If you have COMCAST's telephone modem (which has a battery backup so that it can't be rebooted by simply unplugging it) you can adopt the following procedure to reset the MAC address.
1. Reset the base station, by depressing the reset button in back with a pen or paper clip.
2. Unplug the base station.
3. Reset the Comcast cable modem, by depressing the reset button in the back with a pen or paper clip.
4. Plug the base station back in.
5. Use the Airport Utility to set the parameters of Airport Extreme.
This procedure will force COMCAST to recognize the Base Station MAC Address as legitimate for provisioning.
It's not an ideal solution, but it works. If the Base Station fails and you have to use a direct connection to your computer you can follow a similar procedure to reset the modem, and recognize a new MAC address.
Again, the fact that you can't use the Base-connected drives for Time Machine is just plain dumb. Apple originally touted this as one of their main selling points, and then just backtracked. They need to reintroduce this functionality in the next update of Leopard... and it wouldn't hurt to issue an apology for having misled people. The stone wall just ****** people off, as it should.

Email PDF Form and Sign Entire Submission - Can this lock the form and show the signature?

Thanks to those who explained how to create a button that allows me to email a form as a PDF rather than XML. It helped me a great deal.
Now I want to cause our time sheet adjustment form to be emailed from the employee to their supervisor, and have the form-data be read-only, and the employee signature to be obvious to the recipient.
I've tried checking the Sign Submission check box in the Submit tab of the Button Object window, (where the mailto: tag has been entered.
I clicked the "Settings..." button on the Submit tab and then, under the "Sign Data and Submit Settings" dialog box I selected "Sign Entire Submission". But this does not lock the data and the resulting PDF form once emailed, shows no sign of a signature.
I also tried adding a signature field, and clicked on it to add a signature. But once the signature was added, the Button was disabled and I could not submit the form via the mailto: tag.
Is there a way to signa form with a self-signed signature, and email the entire PDF such that the recipient can see the signature, and that the data are no longer editable?
Wouldn't that just be ducky...?
Thanks again,
-David Bartholomew

Thanks for your comment. I suppose I need to add a context to my intended usage to explain why I want what I described. I want the signature to be apparent so users can see that a submission was signed. These forms that I am considering will replace a paper form used internally within my organization, to request a time card change. They only need to be signed as a pro-forma requirement.
If the electronic forms solution is approved by management, I will make a case that since the network is a closed intranet, there is little consequential likelihood that a fellow employee would forge another's time card change request. And since the new form would be submitted through email, there is a further validation that the email will identify the sender's email address. This proposed electronic submission method is certainly as valid as forms where users cut and paste an image of their signature in a document...
The good news is that since I asked this question, I discovered the samples that came with LCD 8...
An example can be found in the Live Cycle Interactive Purchase Order sample found at [installdir]\EN\Samples\Purchase Order\Interactive.
The interactive Purchase Order sample shows how a collection of fields can be defined and then the signature applied only to the data in the collection. The email button is defined as not included in the collection. This way the signature field can be used, and once the document is signed, the email button remains enabled.
The interactive purchase order sample also demonstrates how a drop down list can be populated by a JavaScript as well as some array handling syntax that I've been looking for.
I recommend the samples to anyone who, like me, may not have been aware of their relevance.
Thanks again, this forum is a great resource.
-David

Why can't I add text in the signature panel in firefox?

why can't I add text in the signature panel in firefox? I have adobe acrobat pro XI. I can open a pdf in acrobat pro and am able to add text to a pdf, but when I open a pdf in firefox, the "add text" option is not available.

When you install Acrobat XI you are also installing Reader for use in the browser. Reader is "sandboxed", or as it says in the Preferences, it is in "Protected Mode". Acrobat does not understand the concept of running in sandboxed memory (sandbox is a security feature to prevent the bad guy from exploiting a memory error and getting into a memory address where they can do damage to your computer) so to help protect Acrobat users the same way Reader users are protected we just install Reader along with Acrobat, but it is only used in the browser (part of this is because the bad guys use web sites as their primary method of distributing corrupted PDF files that can cause problems).
That said, because you are in Reader the file needs to be Reader Enabled prior to being posted to the web site (or opened in the browser). Once the file is Reader Enabled you should be able to add the text annotations.
Steve

I can't find the Signature option in the Annotations menu in Preview

I am trying to add a digital signature that I have already created to a PDF file but there is no Signature option showing up in the Annotations menu in Preview. The document I am trying to add the signature to is definitely a PDF but there is still no signature option showing up. Please help!!!

HI,
I had the same issue,
You need to convert documents to PDF first (Files, export as PDF)
And then you will have the option!
Kind regards.

Two parameters in the SMTP Conector , EXHCANGE 2007

Hello,
   I installed a Exchange 2007 several weeks ago. I registered a domain of my own just 5 or 6 days ago too.
   In "the public side" all seems to be running okay because nslookup points to my Public IP when I ask for the mx record (=mail.mydomain.eu).
   I can't send any email outside the organization.
   ISA server does not see any traffic to port 25 when I send an email from my internal OWA to hotmail o gmail.
   Which makes me think it is something related to the connector is ISA Server not seeing any traffic to port 25.
   I am not an expert in Exchange 2007, but I saw these two parameters in the SMTP Connector:
   1- Specify the FQDN this connector will provide in response to HELO or EHLO.
         It is empty, but it is empty because as an attempt to solve this problem, I deleted the SMTP Connector and created a new one from a wizard, and then I see now this field empty.
2- Use consult External DNS configuration in the Hub Transport Server.
       I don't understand what is the difference of this being ticked or not.
I restarted both ISA 2006 Server and Exchange 2007, just in case, because I feel stuck about what to do next, and besides, since I don't fully understand those two parameters, well, maybe the problem is there.
Thanks in advance!
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Thanks a lot DagDougInc!.
FIRST OF ALL: Now I am able to get to gmail and hotmail, I just removed my smtp connector and created a new one from scratch. And all came to the address space not being set at "*/Cost 1" but at "mydomain.eu/Cost 1". Gosh, since
I am a newcomer, I didn't know better sorry.
The problem now is to receive emails.
1. I am able to reach my email public server, at least its ip, through nslookup:
nslookup
server 8.8.4.4
set type=mx
mydomain.eu
...and this shows up: "Non-Authoritativeresponse : mydomain.eu MX preference = 10, mail exchanger = mail.mydomain.eu"
2. I am also able to reach smtp.gmail.com through telnet, but when "AUTH LOGIN", it says "must issue a STARTTLS command first" , but I guess this is not any issue to take into account.
I have to say that in my 2008 server (where I have Exchange 2007 installed) I have no telnet, nor in one of my LAN clients (Windows 7). I suspect both Windows 2008 and Windows 7 got rid of telnet.
I did it therefore in a 2003 Server which is not inside the LAN (it is outside the LAN and outside the ISA Server) , so, I don't know if it was useful for my problem.
Can I test "telnet mail.mydomain.eu 25" from inside my own router?. My guess is that I can't. Someone explained something about a loop, but I have to dig into it.
3- In my router there is a Virtual server forwarding the smtp traffic to my ISA Server which points to Exchange server in my DMZ, whose traffic is allowed in my firewall, through a Exchange rule (I am used to this, I will check it, but I have done this many
times).
EDITION:
4- ISA Server does not see any smtp traffic when I send an email from gmail to my domain, but it sees smtp traffic when I send emails from my exchange server to gmail. I point this out because in my view, the problem may be outside the ISA, since it does
not see any traffic reaching my network, maybe not even my router.
Again: Thanks a lot !
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Using the Android Reader app, why is the signature option greyed out?

I have a client that has enlisted me to create 3 fillable PDF forms. I used FormsCentral to create these fillable forms, then I saved them as PDFs to my Dropbox. I opened the Adobe Reader app on my Tablet, and access the forms. As for the client, they are home builders, and these 3 forms are 3 different stages of the building process. They are using them to interact with the new homeowner. They want to do this on Samsung Note 10.1 tablets with Verizon data. There are 3 issues I am faced with fixing:
1. The signing process is quite a process. Meaning too many clicks to setup and apply a digital signature according to the customer. And that is on a PC, because I am unable to use the "signature" function - the button is greyed out. Why is that?
2. Once we resolve the above issue, then will there be a way to "lock" the form so that the customer's responses and selections are unchangeable? If so, how?
3. Once the form is signed and "locked" (if possible), what is the simplest way to send the form via e-mail? I ask because they want there to be a way to setup the form to e-mail copies to the addresses that are entered into an e-mail field on the form. Sort of "auto-populate" the addresses as well as be able to set a predetermined address (back to their office) so that the results may be sent via mobile instantly upon completion.
I know that is a lot to ask. Your help would be most appreciated!
Thanks in advance, Rob

(1) Why is the Signature button greyed out (disabled)?
You used FormsCentral to create fillable forms and exported to PDF. When exporting FormsCentral forms to PDF forms, FormsCentral adds "extended rights" to PDF forms so that users can fill out the PDF forms in Adobe Reader (which is a PDF viewer, not a PDF editor).
The current version (11.5.0) of Adobe Reader for Android does not allow signatures to be added to any "Reader Extended" PDF documents (including forms). We are actively investigating and trying to resolve the problem.
(2) Is there a way to "lock" a PDF form?
You can "flatten" a PDF form after the form has been filled out and signed by a customer. Once flattened, it's not possible to change filled data or signatures. When you try to email a filled PDF form (optionally with a signature), Adobe Reader for iOS will present the E-mail Document dialog with two options: "Send Original Document" and "Send Flattened Copy". You can choose the "Send Flattened Copy" option.
Unfortunately, the feature has not been supported in Adobe Reader for Android yet.
(3) What is the easiest way to send a "flattened" copy via email?
Because the issues 1 & 2 above have not been resolved, you are not able to do this in Adobe Reader for Android. However, you can do this in Adobe Reader for iOS.
First, you need to add a Submit button to your PDF form. I am not sure if you can do this in FormsCentral. But you can use Adobe Acrobat (a paid product) to add a Submit button.
Setting action buttons > Add a submit button
When your customer taps the Submit button in the PDF form, Adobe Reader (for iOS - for now) will present thee same E-mail Document dialog. Once the "Send Flattened Copy" option is selected, Reader will launch the default Mail app and auto-populate email address(es) specified for the Submit button action.
Please let us know if you have further questions.

Cant see messages in the External Definitions

I'm imporing following wsdl into XI. However I cant see messages and seems to be there is some error in wsdl. Would someone help me please?..
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:services.soap.a2z.com" xmlns:intf="urn:services.soap.a2z.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:services.soap.a2z.com">
     <wsdl:types>
          <schema targetNamespace="http://xml.apache.org/xml-soap" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="mapItem">
                    <sequence>
                         <element name="key" nillable="true" type="xsd:string"/>
                         <element name="value" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="Map">
                    <sequence>
                         <element maxOccurs="unbounded" minOccurs="0" name="item" type="apachesoap:mapItem"/>
                    </sequence>
               </complexType>
          </schema>
     </wsdl:types>
     <wsdl:message name="exportGroupResponse">
          <wsdl:part name="exportGroupReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importGroupRequest1">
          <wsdl:part name="in0" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importGroupResponse">
          <wsdl:part name="importGroupReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importGroupResponse1">
          <wsdl:part name="importGroupReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importGroupRequest">
          <wsdl:part name="in0" type="xsd:string"/>
          <wsdl:part name="in1" type="apachesoap:Map"/>
     </wsdl:message>
     <wsdl:message name="loadAdaptersResponse">
          <wsdl:part name="loadAdaptersReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="loadAdaptersRequest">
</wsdl:message>
     <wsdl:message name="exportAdapterResponse">
          <wsdl:part name="exportAdapterReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importAdapterRequest1">
          <wsdl:part name="in0" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="exportAdapterRequest">
          <wsdl:part name="in0" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importAdapterResponse">
          <wsdl:part name="importAdapterReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="exportGroupRequest">
          <wsdl:part name="in0" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importAdapterResponse1">
          <wsdl:part name="importAdapterReturn" type="xsd:string"/>
     </wsdl:message>
     <wsdl:message name="importAdapterRequest">
          <wsdl:part name="in0" type="xsd:string"/>
          <wsdl:part name="in1" type="apachesoap:Map"/>
     </wsdl:message>
     <wsdl:portType name="Adapter">
          <wsdl:operation name="importAdapter" parameterOrder="in0 in1">
               <wsdl:input name="importAdapterRequest" message="impl:importAdapterRequest"/>
               <wsdl:output name="importAdapterResponse" message="impl:importAdapterResponse"/>
          </wsdl:operation>
          <wsdl:operation name="importAdapter" parameterOrder="in0">
               <wsdl:input name="importAdapterRequest1" message="impl:importAdapterRequest1"/>
               <wsdl:output name="importAdapterResponse1" message="impl:importAdapterResponse1"/>
          </wsdl:operation>
          <wsdl:operation name="importGroup" parameterOrder="in0 in1">
               <wsdl:input name="importGroupRequest" message="impl:importGroupRequest"/>
               <wsdl:output name="importGroupResponse" message="impl:importGroupResponse"/>
          </wsdl:operation>
          <wsdl:operation name="importGroup" parameterOrder="in0">
               <wsdl:input name="importGroupRequest1" message="impl:importGroupRequest1"/>
               <wsdl:output name="importGroupResponse1" message="impl:importGroupResponse1"/>
          </wsdl:operation>
          <wsdl:operation name="exportAdapter" parameterOrder="in0">
               <wsdl:input name="exportAdapterRequest" message="impl:exportAdapterRequest"/>
               <wsdl:output name="exportAdapterResponse" message="impl:exportAdapterResponse"/>
          </wsdl:operation>
          <wsdl:operation name="exportGroup" parameterOrder="in0">
               <wsdl:input name="exportGroupRequest" message="impl:exportGroupRequest"/>
               <wsdl:output name="exportGroupResponse" message="impl:exportGroupResponse"/>
          </wsdl:operation>
          <wsdl:operation name="loadAdapters">
               <wsdl:input name="loadAdaptersRequest" message="impl:loadAdaptersRequest"/>
               <wsdl:output name="loadAdaptersResponse" message="impl:loadAdaptersResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="AdapterServiceSoapBinding" type="impl:Adapter">
          <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="importAdapter">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="importAdapter">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="importGroup">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="importGroup">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="exportAdapter">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="exportGroup">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="loadAdapters">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:services.soap.a2z.com"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="AdapterService">
          <wsdl:port name="AdapterService" binding="impl:AdapterServiceSoapBinding">
               <wsdlsoap:address location="http://vn15:8000/soap/services/AdapterService"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>

Hi S T,
in the WSDL there occurs the situation that there are in one prtType multiple operations with the same name (e.g. portType "Adapter" contains two definitions for operation with name "importAdapter". Indeed, the original <a href="http://www.w3.org/TR/wsdl">WSDL specification</a> seems to allow this. However, in <a href="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html">WS-I</a> it is forbidden (see R2304).
Therefore, the Integration Builder does not consider this document to be valid WSDL. This is a little bit tragic, as the portType definitions are not considered by the following steps anyway. A simple workaround would be to delete everything behind the message definitions.
Greetings Stephan

Address parameters in the signature definitions (4.1)

Similar Messages

Maybe you are looking for