Per-message signature or Encryption in iOS 6?

Can someone tell me if:
1. There is a way to do per-message digital sigantures AND digital Encryption in iOS 6, AND
2. There is a way to cause the default behavior to be to return an encrypted e-mail with an encrypted e-mail? The default is to return an unencrypted e-mail (in iOS 5), and that's clearly the wrong thing to do.
Rob

Robert Cunningham wrote:
Can someone tell me if:
1. There is a way to do per-message digital sigantures AND digital Encryption in iOS 6
Not until iOS 6 becomes available to the general public which happens later today.

Similar Messages

With per-message S/MIME enabled, the default action when replying to an encrypted message is to send that reply unencrypted. Causes users to accidentally send originally encrypted content, back unencrypted.

This seems counter-intuitive, are we doing something wrong or is this working as expected?
When we have per-message S/MIME enabled on an iOS 8 device. Everything works as expected and we have the ability to select when you are sending an email whether that email should be encrypted or not, but i've noticed that, when you receive an email encrypted with your S/MIME cert, read that email on your iOS8 device with per-message S/MIME enabled, and reply to, or forward, that message, the default action is to send that reply, or forward, unencrypted UNLESS you manually re-tap the little padlock button to re-encrypt the message.
This seems broken. I would imagine we would want the default action when replying or forwarding that encrypted message to be an encrypted reply or forward so as to keep the encryption intact. I can't think of a time when you would actually want to send an unencrypted reply to an encrypted message, as doing so would send the originally encrypted content back, as unencrypted text therefore negating the point of ever encrypting it in the first place.
I know we can set the iOS device to by default send ALL email as encrypted, but that's overkill. Our users probably only get 1 or 2 encrypted emails a week, but when they do get those encrypted email we would want their replies and forwards to those email to also remain encrypted, and not open up the chance of one of these users forgetting to re-check the padlock button thus accidentally sending the originally encrypted content, out as an unencrypted message.
Is this working as expected or are we doing something wrong?

Hi,
Thank you for your clarification.
Yes, it seems you have installed all the updates for the Outlook.
“Testing on a good computer” is a method to narrow down whether the cause is related a specific computer.
For debugging tool, I think we can take a look at:
1. RPCTrace log
2. Process Monitor
For RPCTrace log, it’s not that easy to capture. You must firstly replace some Outlook dll files before you can capture the log. Even more, the dll files can vary if the Outlook
SP versions are different. So, It’s recommend to contact a Microsoft Support to capture and analyze the trace log.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

MIME/SMIME Encryption with Bad Message Signature error

Hello Gurus,
I'm trying to send out an encrypted message through a custom pipeline with MIME Encoder. The error we're getting is: The message has a bad message signature. I searched around and found no references to this error.
All the certs are in place. Encryption was set to true in the pipeline. No signing needed.
Has anyone run into this issue before? Thank you in advance.

The error we're getting is: The message has a bad message signature. I searched around and found no references to this error.
Hi,
According to current information, we can hardly give precise troubleshooting why this happens, I think you need check the configuration on your side, and collect more information for us to troubleshoot.
Regards
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Digital Signatures and Encryption in Yosemite Mail

After upgrading to Yosemite, I am having difficulty using the Mac Mail app to send digitally signed and encrypted email.
Before the upgrade to Yosemite, I was able to send signed and encrypted emails using certificate/keys in my keychain using both the Mac Mail app and Microsoft Outlook 2011 for Mac.
After upgrading, I am still able to send signed and encrypted message in Outlook, but the Mac Mail app gives the following error when I attempt to send a signed email:
'You don’t have a trusted certificate in your keychain that matches the email address “XXXX@XXXX”. Without a certificate, you can’t sign messages sent from this address.' (Actual name replaced)
When I look at my certificates in my keychain, a certificate is available with "Usage: Digital Signature" that has the email address from the error message "XXXX@XXXX" with exact case in the RFC 822 Name.
Another interesting piece of data that might help track this down is that when I first launch the Mac Mail application, the Mac Mail application is able to successfully decrypt emails that have been previously sent encrypted to me. HOWEVER, after I attempt to send an email and get the "You don’t have a trusted certificate..." error message, these emails are no longer able to be decrypted. I get the "Unable to decrypt message" header above the message and the content of the message is just a "smime.p7m". If I close the mail application and restart it, these encrypted message are once again decrypt-able until I attempt to send a message.
It almost seems like things are working until mail tries to access the keychain.
I have attempted to delete my certificate and keys from my keychain and then adding those items again.
I have attempted to close the mail application and reopen it.
I have attempted to reboot my computer.

1. I want to confirm that this is still an issue for me in 10.10.1 and mail Version 8.1 (1993)
2. I have another data point.
At my office I have wired networking and wireless networking available. Primarily I utilize the wired networking for access to network drives, etc.
When using the wired networking, I experience all the problems that have been catalogued in this thread. Can't sign, can't encrypt, can't close the compose window after the mail program fails to find my certificate.
However, when I switch to wireless networking before starting the mail application, digital signatures and encryption seem to work! This is pretty weird behavior. Make sure to restart mail if you were previously wired.
Here are some theories:
Something to do with OCSP? When I am wired vs wireless I am on different ip subnets and subject to different firewall rule sets. Perhaps OCSP is trying to determine the status of the certificate and failing?
Here are some things I have tested:
I switched to a different official apple brand thunderbolt to ethernet adapter with no change in behavior
I disabled wireless and disconnected my wired network. So no network access at all. Signatures and encryption work! The message obviously does not send, but it appears in my outbox and I don't get the signature error. When I reconnect my wired cable, the message sends successfully and appears as encrypted in my sent folder!
I have attempted to disable OCSP by using "Keychain Access --> Preferences --> Certificates Tab --> OCSP (OFF) and CRL (OFF)" but this hasn't made a difference in the behavior of wired networking.
Ran a TCPDUMP on traffic to the OCSP service but didn't see any traffic when I attempted to send a message and received the signature error
I am pretty stumped on this. This is very odd behavior
Does anyone else experience this behavior?

Creating a signature and Encrypt the file

Hi Experts,
I have an requirement, I need to create a module in which I need to pass four values (Namely signing key, signing algorithm, encyption key and encryption algorithm) through parameters as inputs. Based on these parameters, I need to create the signature for the input xml file and I have to encrypted the file. Please Guide me. Give some useful links, documents or codes to how to do this. Help me in this regard.
Thanks in Advance,
Venkatesh.K

Hi,
Digitally signing of messages is possible by using cryptographic toolkits.
All required java programs are imported as archives into XI. Java mapping is written utilizing the imported java archives which actually performs the digital signature creation for the outgoing messages from XI and digital signature verification for the incoming messages to XI.
refer
SAP Network Blog: Using Digital Signatures in XI
/people/sap.user72/blog/2005/06/16/using-digital-signatures-in-xi
SAP Network Blog: How to use Digital Certificates for Signing & Encrypting Messages in XI
/people/varadharajan.krishnasamy/blog/2007/05/11/how-to-use-digital-certificates-for-signing-encrypting-messages-in-xi
SAP Network Blog: How XML Encryption can be done using web services security in SAP NetWeaver XI
/people/aparna.chaganti2/blog/2007/01/23/how-xml-encryption-can-be-done-using-web-services-security-in-sap-netweaver-xi
You may also use the SAP cryptographic toolkit available from SAP market place for signing encrypting. See i.e. http://help.sap.com/saphelp_nw04/helpdata/en/4f/65c3b32107964996a56e4165077e24/frameset.htm
Decryption of Message after processing by File adapter
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/thread.jspa%3FforumID%3D44%26threadID%3D37512
Ensure the Confidentiality of Your SOAP Message Content: XML Encryption Using Web Services Security in SAP NetWeaver Exchange Infrastructure
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0650f56-7587-2910-7c99-e1b6ffbe4d50
Digital Signatures in SAP Applications
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40f6fee6-9316-2a10-d2a9-954d4df7dd33
Best Practices for Digital Signatures
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/55ba9790-0201-0010-aa98-ce8f51ea93cd
Thanks
Swarup
Edited by: Swarup Sawant on Apr 4, 2008 2:02 PM

Per account signature not switching in Mail

Since upgrading to Mountain Lion the per account signature feature in Mail is not operating accurately.
When I compose a new message a signature appears (signature A). When I select a different account to send from in the FROM list the new signature (signature B) appears, but the one that was there originally no longer disappears (leaving me with signature A & B on the message).
Thoughts?

Monolith19,
This happened to me, but I think I found a fix. I think the problem happens with signatures that were created in a prior version of Mail.
Go to Mail > Preferences > Signatures, select the signature that isn't disappearing properly and copy/paste its contents into something like TextEdit so you have a backup.
Delete the signature.
Create a new signature with the name of your old signature. Paste the contents of your old signature into it.
In the left panel, choose the mail account you want to use the signature with, and select your new signature from the Choose Signature popup list.
That's it. Now it works as expected.
Good luck,
Dave

Message signature for NTLMv2 Authentication message

Hi,
I'm implementing NTLMv2 support for SMBv2 and I have encountered some problems calculating the correct checksum for the authentication message.
Authentication packet:
4E 54 4C 4D 53 53 50 00 03 00 00 00 18 00 18 00 AE 00 00 00 42 01 42 01 C6 00 00 00 1E 00 1E 00 58 00 00 00 1A 00 1A 00 76 00 00 00 1E 00 1E 00 90 00 00 00 10 00 10 00 08 02 00 00 15 82 88 E2 06 01 B1 1D 00 00 00 0F 57 7C 17 17 5E DF 25 D8 8C 06 8D E6 75 5F
62 65 57 00 49 00 4E 00 2D 00 34 00 37 00 50 00 30 00 39 00 4E 00 51 00 42 00 4B 00 49 00 38 00 41 00 64 00 6D 00 69 00 6E 00 69 00 73 00 74 00 72 00 61 00 74 00 6F 00 72 00 57 00 49 00 4E 00 2D 00 51 00 32 00 33 00 49 00 36 00 4F 00 34 00 55 00 55 00 44 00
53 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 67 E7 1D 8A 39 CC A0 52 A7 01 51 02 E9 5A DF 7B 01 01 00 00 00 00 00 00 7F D2 02 FD 80 6C D0 01 2A 01 01 16 D7 E9 11 F7 00 00 00 00 02 00 1E 00 57 00 49 00 4E 00 2D 00 34 00 37 00
50 00 30 00 39 00 4E 00 51 00 42 00 4B 00 49 00 38 00 01 00 1E 00 57 00 49 00 4E 00 2D 00 34 00 37 00 50 00 30 00 39 00 4E 00 51 00 42 00 4B 00 49 00 38 00 04 00 1E 00 57 00 49 00 4E 00 2D 00 34 00 37 00 50 00 30 00 39 00 4E 00 51 00 42 00 4B 00 49 00 38 00
03 00 1E 00 57 00 49 00 4E 00 2D 00 34 00 37 00 50 00 30 00 39 00 4E 00 51 00 42 00 4B 00 49 00 38 00 07 00 08 00 7F D2 02 FD 80 6C D0 01 06 00 04 00 02 00 00 00 08 00 30 00 30 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 20 28 45 5A F8 71 0C F9 CC 5A EB A1
F5 FB C3 17 49 CE 76 FF 1B 32 31 4D 52 E7 0E D8 B0 BA C5 F9 0A 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09 00 22 00 63 00 69 00 66 00 73 00 2F 00 31 00 39 00 32 00 2E 00 31 00 36 00 38 00 2E 00 31 00 2E 00 31 00 31 00 00 00 00 00 00 00 00 00
00 00 00 00 03 AC 9B EA 78 DD DF 49 BB D8 2D 66 0C 4F 22 61
By offline testing of packets I was able to get
ExportedSessionKey: 945d257f88b6be1a4b201748e3f134c5
and from there calculate the correct MIC (based on the negotiation,challenge and authentication messages).
But now when I am trying to calculate the checksum for the message signature I can't get this right.
The SignKey equals to md5(concat(ExportedSessionKey,"session key to client-to-server signing key magic constant")):
2643d035ac56345368b321df5059f9b0
The SealKey equals to md5(concat(ExportedSessionKey,"session key to client-to-server sealing key magic constant"))
dbb66166a80c4be9b876a6f4ec1dd3a5
and the sequence number is: 0
I'm using this function to calculate the checksum:
rc4(sealKey,hmac_md5(SignKey,concat(Sequence Number,message) ) ) [0 .. 7] = 0790d273a21186ce
That's an incorrect checksum, the real checksum should have been: 524102bf5e86c109 (captured from the packet).
These are the negotiation flags of this session that are set:
NegotiateUnicode,RequestTarget,NegotiateSign,NegotiateNTLM,NegotiateAlwaysSign,NegotiateNTLM2,
NegotiateTargetInfo,NegotiateVersion,Negotiate128,NegotiateKeyExch,Negotiate56
The only thing I wasn't sure about is if I need to calculate the checksum from the message with Z(16) instead of the mic or with the real calculated mic. Nevertheless I don't get the checksum on both ways.
I've also added the packets from the relevant session.
https://www.dropbox.com/s/eepcpmim3rj2zkd/ntlm.cap?dl=0
Thanks in advance!

Hi Guy:
The details for how to calculate a MechListMIC are described in RFC 4178 (http://www.rfc-editor.org/rfc/rfc4178.txt) section 5(a).
Any details specific to Windows are described in MS-SPNG (https://msdn.microsoft.com/en-us/library/cc247021.aspx) documents.
I will give you an example here how the client calculates MechListMIC in case of NTLM.
For this example, I used an actual SMB2 session set up exchange. If you need the network trace that I used, please send an email to dochelp at microsoft dot com to my attention referencing this thread.
server challenge: 0x91, 0xA7, 0xB5, 0xA0, 0x93, 0xD1, 0x28, 0x73
Password: Password01!
client's MechTypes from first session set up message : 30 0C 06 0A 2B 06 01 04 01 82 37 02 02 0A
Security blob from the session set up command that contains the authenticate message:
A1 82 01 CD 30 82 01 C9 A0 03 0A 01 01 A2 82 01
AC 04 82 01 A8 4E 54 4C 4D 53 53 50 00 03 00 00
00 18 00 18 00 86 00 00 00 FA 00 FA 00 9E 00 00
00 0C 00 0C 00 58 00 00 00 06 00 06 00 64 00 00
00 1C 00 1C 00 6A 00 00 00 10 00 10 00 98 01 00
00 15 82 88 E2 06 03 80 25 00 00 00 0F 82 C4 C5
F7 7B 08 49 FD A2 87 0E A3 05 EC 77 AB 66 00 6F
00 72 00 4D 00 44 00 4D 00 61 00 62 00 63 00 4D
00 49 00 4E 00 49 00 4E 00 54 00 2D 00 36 00 37
00 31 00 30 00 38 00 46 00 4B 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 30 0B A0 EF 0B 39 38 45 54 E6 ED 4F B4
FD 6D B6 01 01 00 00 00 00 00 00 72 23 6C 58 68
6D D0 01 B5 FF F2 9D 10 1B 35 60 00 00 00 00 02
00 0C 00 46 00 4F 00 52 00 4D 00 44 00 4D 00 01
00 0C 00 46 00 4F 00 52 00 4D 00 44 00 4D 00 04
00 0C 00 66 00 6F 00 72 00 4D 00 44 00 4D 00 03
00 0C 00 66 00 6F 00 72 00 4D 00 44 00 4D 00 07
00 08 00 72 23 6C 58 68 6D D0 01 06 00 04 00 02
00 00 00 08 00 30 00 30 00 00 00 00 00 00 00 01
00 00 00 00 20 00 00 15 7C 95 BD E7 02 DE 3B C9
8D F1 46 91 04 AC 4D 16 61 03 F1 BF 42 77 85 B2
82 B7 83 2E CB 1E 3F 0A 00 10 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 09 00 22 00 63
00 69 00 66 00 73 00 2F 00 31 00 39 00 32 00 2E
00 31 00 36 00 38 00 2E 00 31 00 2E 00 34 00 30
00 00 00 00 00 00 00 00 00 00 00 00 00 8E 07 9F
C9 F1 50 97 65 F3 BD A8 C1 32 8A 52 56 A3 12 04
10 01 00 00 00 3B 1F D5 E0 2D 97 5F 97 00 00 00
00
My calculation are from servers perspective. Everything server needs to verify client's MechListMIC
is in the security blob and what is not in blob is already with the server (password, server challenge and client's MechTypes sent in an earlier message).
The KeyExchangeKey is NTLMv2 session base whose calculation is described in MS-NLMP (https://msdn.microsoft.com/en-us/library/cc236621.aspx) section "3.3.2 NTLM v2 Authentication"
KeyExchangeKey (NTLMv2 session base key)=ad6e6c75872afd2178533d2ebb8ad9ad
Using KeyExchangeKey to RC4 decrypt the Encrypted Random Session key, we get
Random Session Key: c7 9a 31 b6 8d b6 4e 3f 84 66 be a3 b2 22 3b c1
Using Random session key above and description in MS-NLMP, we calculate the signing and sealing keys.
Server Signing Key: 69 cb 53 69 d5 18 75 04 dc 7e 61 03 33 10 53 e9
Server Seal Key: 35 4e c9 d1 86 2d 4f a5 98 25 87 c4 b5 35 f2 33
Client Signing Key: a2 b2 1a ed a9 ec d3 f1 3d ff c3 3d e0 1b 59 30
Client Seal Key: 1e bb c6 f3 65 5b dc 13 b3 5b e4 e2 24 eb 71 e2
Now using the client signing and sealing keys, we proceed to calculate the NTLM signature of client's MechTypes as described in MS-NLMP section "3.4.4.2 With Extended Session Security":
Message number is 00 00 00 00
MechList with 0000 concatenated:
00 00 00 00 30 0c 06 0a 2b 06 01 04 01 82 37 02 02 0a
HMAC_MD5 of the above using client signing key (first 8 bytes): 28 d5 e1 57 a4 d4 58 24
checksum (RC4 encrypting the above using Client Sealing key): 3b 1f d5 e0 2d 97 5f 97
MechListMIC by appending version and sequence: 01 00 00 00 3b 1f d5 e0 2d 97 5f 97 00 00 00 00
As you can see this matches with what client sent.
Please let me know if it does not answer your question.
Regards, Obaid Farooqi

Why won't my message signature verify

Can anyone help. I dont seem to be able to verify a signature that I have just created. I'm a Java and Crypto newbie so please take it easy on me! The code is as follows:
import java.nio.ByteBuffer;
import java.security.KeyPair;
import java.security.KeyPairGenerator;
import java.security.Signature;
public class EncryptionLesson {
     public static void main(String[] args) throws Exception {
          ByteBuffer message = ByteBuffer.wrap("This is my message".getBytes());
          // Create key pair
          KeyPairGenerator kpg;
          kpg = KeyPairGenerator.getInstance("DSA");
          kpg.initialize(512);
          KeyPair pair = kpg.genKeyPair();
          // Sign a message
          Signature sig = Signature.getInstance("DSA");
          sig.initSign(pair.getPrivate());
          sig.update(message);
          ByteBuffer messageSignature = ByteBuffer.wrap(sig.sign());
          // Verify signature
          Signature vsig = Signature.getInstance("DSA");
          vsig.initVerify(pair.getPublic());
          vsig.update(message);
          if (vsig.verify(messageSignature.array())) {
               System.out.println("Signature Okay");
          } else {
               System.out.println("Signature NOT Okay");
}The result is alway "Signature NOT Okay". Please excuse the gratuitous use of ByteBuffer, I have just read JavaNIO and was sold on them.

sorry about mistaking the vaiables in the previous post. the proper main will look like this:
public static void main(String[] args) throws Exception {
          ByteBuffer message = ByteBuffer.wrap("This is my message".getBytes());
          // Create key pair
          KeyPairGenerator kpg;
          kpg = KeyPairGenerator.getInstance("DSA");
          kpg.initialize(512);
          KeyPair pair = kpg.genKeyPair();
          // Sign a message
          Signature sig = Signature.getInstance("SHA1withDSA");
          sig.initSign(pair.getPrivate());
          sig.update(message.array());
          ByteBuffer messageSignature = ByteBuffer.wrap(sig.sign());
          // Verify signature
          Signature vsig = Signature.getInstance("SHA1withDSA");
          vsig.initVerify(pair.getPublic());
          vsig.update(message.array());
          if (vsig.verify(messageSignature.array())) {
               System.out.println("Signature Okay");
          } else {
               System.out.println("Signature NOT Okay");
     }Futher to bring it to your notice, this is signing and verification and not encryption ;-) you might consider your class name!

Recordset per message in Sender File Adapter

Hi Friends
I have configured a sender file adapter to pick up *.txt files from a specific path, Since the file is having thousands of records it is failing to process the file at PI level . In order to avoid the problem I have kept Recordset Set Per Message as 10 , but still PI is processing all the records into a single message. Please help me in troubleshooting it.
Regards
Suman.

Hi Suman,
Go thru these threads for troubleshooting...
Massive file
Processing huge file loads through XI
Processing of huge no of Inbound xml files
Bottleneck in Large file processing
How to process large data files in XI ? 100 MB files ?
Regds,
Pinangshuk.

TS2755 Messages no longer works with iOS 6.

Messages no longer works with iOS 6. Done all the checks, everything that's recommended. Zilch

Had the same problem after updating to ios 6 could not send-recieve text messages at all. Did a restore on iphone same problem, changed setting same problem. called at&t they said they is a problem the ios 6 that changes setting at att take techline 15 minutes and imessage and text messages working ok

Recordsets per Message not working

I found that Recordsets per Message will split the source message into multiple messages and process them separately. This will save my alot of time and is exactly what I need - but it does not work.
I have in my sender file adapter the following parameters in File Content conversion:
Document Name = MT_SND_ZADIG
Document Namespace = urn://federalmogul.com/ADP/FINFRADP001/00
Recordset Name = RECORDSET
Recordset Structure = RECORDSET,*
Recordset Sequence = Ascending
Recordsets per Message = 10
Key Field Type = String (case-sensitive)
RECORDSET.fieldNames RECORDCODE,ACCOUNTID,CONST_E,CONST_Z2M,MONTHYEAR,JOURNALCODE,FOLIOCODE,RECORDTYPE,DAY,GLACCOUNT,CODINGBLOCK,DEBITAMOUNT,CREDITAMOUNT,TEXT,FILLER1,FILLER2,ACCREF1,ACCREF3,EMPLOYEENO,REPORTTYPE,ZADIGCODE,ACC_TYPE,RESERVED,CENTURY
RECORDSET.fieldFixedLengths 2,6,1,3,4,3,2,1,2,12,18,13,13,20,8,8,12,12,6,4,6,1,1,2
RECORDSET.lastFieldsOptional yes
When I feed in a file with 77 records I would expect it to split it into 7 * 10 recordset and then 1 * 7 - why is it not doing this?

Hi Lynn,
And... what is the result you are getting?
Try to change Recordset Structure with something different that Recorset name.
Something like:
Recordset Name = RECORDSET
Recordset Structure = row,*
row.fieldNames RECORDCODE,ACCOUNTID,CONST_E,CONST_Z2M,MONTHYEAR,JOURNALCODE,FOLIOCODE,RECORDTYPE,DAY,GLACCOUNT,CODINGBLOCK,DEBITAMOUNT,CREDITAMOUNT,TEXT,FILLER1,FILLER2,ACCREF1,ACCREF3,EMPLOYEENO,REPORTTYPE,ZADIGCODE,ACC_TYPE,RESERVED,CENTURY
row.fieldFixedLengths 2,6,1,3,4,3,2,1,2,12,18,13,13,20,8,8,12,12,6,4,6,1,1,2
row.lastFieldsOptional yes
Follow the example is described in:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,
Carlos

Digital Signatures and Encryption

I recently attended the webinar on Web Services interoperability w/ .NET. The
presenter mentioned that digital signatures and encryption did not work w/ Workshop
8.1. Is it fixed in 8.1 SP2? Also, are there any interoperability issues w/
.NET and Workshop using digital signatures and encryption.

Hi Amber,
The work is based on the finalization and imminent publication of the
wsse Oasis spec. This is targeted for WLS 8.1 SP3, and you can contact
our outstanding support organization, reference CR134931, for details.
Regards,
Bruce
Amber Osterman wrote:
>
I recently attended the webinar on Web Services interoperability w/ .NET. The
presenter mentioned that digital signatures and encryption did not work w/ Workshop
8.1. Is it fixed in 8.1 SP2? Also, are there any interoperability issues w/
NET and Workshop using digital signatures and encryption.

Sender File Adapter cannot send single record per message ?

Hi,
I have scenario flat file to jdbc. but then why the sender file adapter didn't split the record to become single record per message eventhough i have set it in "Recordsets Per Message" = 1. ?
Document Name               MT_APINVOICE
Document Namespace          urn:file:jdbc:apivinvoice
Document Offset               8
Recordset Name               INPUT
Recordset Namespace
Recordset Structure                          RECORD,*
Recordset Sequence                          Ascending
Recordset per Message          1
Key Field Name
Key field Type               String
RECORD.fieldFixedLengths     10,5,10,10
RECORD.endSeparator     'nl'
RECORD.fieldNames          F1,F2,F3,F4
Please advise
Thank You and Best Regards
Fernand

>>but then how to make for example more then 1 records per message.
like 10 records per message. should i set RECORD,10 ?
That is right. Just try it out yourself.
@Shesagiri,
Number of record is decided by the parameter Recordset structure and number of recordset with in a message is decided by Recordset per Message.
Regards
Jaishankar

File SENDER - "Recordsets per message" being ignored..

Hi
I have a file to file scenario
Sender file:
A1,A2,A3
B1,B2,B3
I want to split the SENDER/SOURCE file in the adapter (NO BPM) so that I am creating n number of RECEIVER files - ONE for each line.
I am trying to use content conversions and setting "Recordsets per message" to 1 but it is completely ignoring this. and ONLY creating 1 file.
I am NOT using any mapping and we are running PI 7.0
Please help
Cheers

Hi
As per my knwoledge you can split files at mapping level in integration engine but at adapter engine you are trying that is FCC which will just convert the data into XML.In FCC it will never split files, you have to do it at mapping level.
Kindly check this link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/600b455f-01cd-2b10-0cab-a50e47a8f800?quicklink=index&overridelayout=true
this is a step by process for your query.
Regards,
Nutan

Group Message not working iPhone 6/ iOS 8

I am not able to receive group messages after I updated to iOS 8.0.2 I just activated my iPhone 6 about 3 weeks ago (Before the Apple pay update). It was working fine until I updated the software with the Apple Pay. Initially I thought ALL the group messages are not working. After few trials I realized it was only the case when the group included both iPhone and non-iPhone users. Groups with ALL iPhone users is working fine.
I have checked everything possible, but nothing works.
- Turned off-on iMessages
- Turned off-on Group messages
- Reset Network Setting
- Erased and Reset the Entire phone from Phone settings (Now operating on iOS8.1)- still not working
- Called my carrier and they didn't seem to understand why I was having this problem
I then spoke with Apple Support who ran few diagnostic tests and they didn't find anything. They suggested that I re-set the phone to brand new phone (with out iCloud back-up) via iTunes (not from phone settings) and see if that will fix this. I will try this later tonight and see if I have any luck.
I tried telling customer service that I want to return my phone and get a new one- but they seemed to keep me away from that option.
Has anyone else experienced this? If so, any suggestions?

Send a group message with your iPhone, iPad, or iPod touch - Apple Support
Send messages with your iPhone, iPad, or iPod touch - Apple Support
iOS: Troubleshooting Messages - Apple Support

Per-message signature or Encryption in iOS 6?

Similar Messages

Maybe you are looking for