Dialog for selecting certificate when creating a signature

When creating a digital signature in Adobe Professional 7 a dialog is presented to the user showing the certificates available to the user. The properties of the certificates shown are: Name, Issuer, Storage Mechanism and Expiry time.
The problem then arises when several certificates are issued to the user from the same CA with the same expiry date... For a "normal user" it is not possible to distinguish between the certs.
Is it possible to modify this dialog to show other information, e.g. Friendly name?
Is it possible to filter the list of certificates shown by e.g. Extended Key Usage OIDs present in the certificates?
Thanks
Kjetil

May be you can try inserting Image as signature
Jyothi

Similar Messages

  • Cannot select name when creating new DC

    Hi all,
    It seems I encounter this kind of problems over and over again when dealing with NWDI )-:
    In this thread Cannot select vendor when creating new DC I couldn't select vendor.
    I installed a new NWDI system (version is 7.18), did all the post installation steps including the configuration of a name server on the SLD but I cannot select "name" and the vendor I entered is not shown (even if enter it manually I cannot select name so it doesn't help - see snapshot).
    [snapshot|http://img134.imageshack.us/i/nwdi.jpg/]
    Snapshot: http://img134.imageshack.us/i/nwdi.jpg/
    I did name server config on : http://server:port/dtr/system-tools/administration/NameServerConfiguration
    Name prefixes are defined under 'Name Reservation -> Development Component Name' - I used <x.y>/* and <x.y>/tst (x.y is namespace like com.omri).
    I updated CMS after setting the name server, restart J2EE and did all kind of voodoo without success.
    I use local SLD which is part of the J2EE.
    I don't get any error messages (from NWDI/SLD/NWDS).
    I don't remember this kind of problem with NWDI on 6.40 versions.
    Moreover I installed and configured several systems on 7.12 & 7.13 versions without any problems but with 7.14 & 7.18 I've problem with setting the name server...
    Please help,
    Thanks,
    Omri

    Solved it on my own by deleting and creating the track again (with the same settings!!!)

  • Which BW variable is used for date(range) when creating a portal service

    Hi,
    Can any one please let me know which BW variable is to be used for date(range) when creating a portal service for searching based on dates.
    Thanks
    Abhai

    Hi Arun,
    its just a portal service which would be called when  searching a document created on a particular date or betwwen a range of date.so what i require is which BW variable to be used when handling range.As for variable technical name we use VAR_NAME_I  and for single value variable we VAR_VALUE_EXT_I
    in the similar manner i want BW variable to be used for range of values.
    Thanks
    Abhai

  • Help diagnosing "The selected certificate has errors: Invalid Signature"

    I am unable to sign a PDF using a new certificate I have received.  I have tried Acrobat X and XI.  I have also tried importing both the root and issuing CAs as trust anchors.  Those certs seem to verify fine.  This issue appears to be with the signature on my cert.
    My suspicion is that the issue stems from the issuing CA's use of the "AlternateSignatureAlgorithm", 1.2.840.113549.1.1.10 RSASSA-PSS, for my user cert.  Acrobat does not seem to recognize this algorithm.  It simply lists the OID value when I look at the signature algorithm under details.
    The certificate is validated fine using certutil.exe and works fine when I use it for client SSL authentication.  I am using Windows 7 and have tried both 32 and 64 bit PCs.
    Has anyone experienced this before?
    ================ Certificate 0 ================
    ================ Begin Nesting Level 1 ================
    X509 Certificate:
    Version: 3
    Serial Number: 100000
    Signature Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
        Algorithm Parameters:
        05 00
    Issuer:
        CN=xyz QA CA
        O=xyz Technical Resources Ltd
        C=US
    NotBefore: 11/15/2012 2:14 PM
    NotAfter: 11/16/2022 2:14 PM
    Subject:
        CN=xyz Issuing CA
    Public Key Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
        Algorithm Parameters:
        05 00
    Public Key Length: 2048 bits
    Public Key: UnusedBits = 0
        0000  30 82 01 0a 02 82 01 01  00 e3 0b d4 99 e6 01 f1
        0010  0e a4 e1 82 8a 8c 39 27  62 7a 03 23 fe 03 3f b5
        0020  0d b6 fa c2 1b 86 44 d6  2f 76 65 b0 02 ff 83 69
        0030  b7 6a 8d b2 d7 22 74 e3  04 9a 01 ec 4c 0f de ff
        0040  c3 db 8f b5 c1 d3 7d 80  f5 ca cc ca 6d ef df 2a
        0050  31 25 18 0b 92 1b 4b 1f  41 c0 5f b6 b2 7e f4 43
        0060  99 43 01 cf c2 60 de 79  75 ec dc 61 11 ea 87 d0
        0070  76 56 a6 4f 00 4a 31 94  37 a5 37 7b 0d 61 49 74
        0080  67 88 31 df 81 16 a2 ed  5c 77 6b 23 6b 92 35 c8
        0090  b3 05 cc 5a 06 3c a3 b3  6c d8 ad 1e 66 28 4e 90
        00a0  3f ad 66 db 6d 13 dd c8  44 29 a0 4f 62 9c f5 5a
        00b0  c1 7e 84 fc e6 24 57 c2  bd ce f1 80 b7 bd 13 b8
        00c0  9f d1 8a bb 41 43 67 9f  68 25 f6 a6 a2 be 44 89
        00d0  11 4f 12 3d 2d d3 85 be  38 f9 97 bd e1 ce 5c 8c
        00e0  4e d4 ce be 19 0b a7 91  5d ee 1e c1 84 2c 2a 5e
        00f0  bb e5 4a fb 7f 2a f4 b8  06 2b 63 1f d9 c3 d9 d3
        0100  5a 13 2d ea 19 63 dd 7c  e5 02 03 01 00 01
    Certificate Extensions: 9
        2.5.29.19: Flags = 1(Critical), Length = 5
        Basic Constraints
            Subject Type=CA
            Path Length Constraint=None
        2.5.29.14: Flags = 1(Critical), Length = 16
        Subject Key Identifier
            8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
        2.5.29.15: Flags = 1(Critical), Length = 4
        Key Usage
            Certificate Signing, Off-line CRL Signing, CRL Signing (06)
        2.5.29.35: Flags = 1(Critical), Length = 7e
        Authority Key Identifier
            KeyID=c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
            Certificate Issuer:
                 Directory Address:
                      CN=xyz QA CA
                      O=xyz Technical Resources Ltd
                      C=US
            Certificate SerialNumber=00 96 b6 de 15 a7 4b 97 ac
        2.5.29.31: Flags = 0, Length = 36
        CRL Distribution Points
            [1]CRL Distribution Point
                 Distribution Point Name:
                      Full Name:
                           URL=http://pki.xyzre.qa1/crls/root-ca.crl
        1.3.6.1.5.5.7.1.1: Flags = 0, Length = 37
        Authority Information Access
            [1]Authority Info Access
                 Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
                 Alternative Name:
                      URL=http://pki.xyzre.qa1/root-ca.cer
        2.5.29.32: Flags = 0, Length = 6e
        Certificate Policies
            [1]Certificate Policy:
                 Policy Identifier=2.16.840.1.101.3.2.1.48
                 [1,1]Policy Qualifier Info:
                      Policy Qualifier Id=CPS
                      Qualifier:
                           http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/documents/test_policy.pdf
        1.3.6.1.4.1.311.21.1: Flags = 0, Length = 3
        CA Version
            V0.0
        1.3.6.1.4.1.311.20.2: Flags = 0, Length = c
        Certificate Template Name (Certificate Type)
            SubCA
    Signature Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
        Algorithm Parameters:
        05 00
    Signature: UnusedBits=0
        0000  41 a4 3f 79 99 d2 aa fa  f9 4b 88 0c a6 be 6f 40
        0010  0b df 10 93 f5 bb 48 c7  1f 89 73 73 09 58 b4 22
        0020  f2 b8 0f 78 b1 da 16 81  cd 2d 86 5a 22 90 67 cd
        0030  22 03 56 d5 c2 f4 df 79  b2 2a 82 e0 2e 5a 9a c3
        0040  92 b5 4d f2 fe 3d 6b f0  97 b0 b7 85 b6 e9 99 4c
        0050  f5 87 34 81 bc 27 f0 77  a1 c6 b2 50 b1 c8 b6 2f
        0060  6f 01 61 0d 1d bc cd 3b  07 2d 18 71 d3 f1 f2 03
        0070  78 e6 82 24 27 b1 65 d5  4b be 6c 20 f7 60 30 4c
        0080  49 42 07 4c 13 d9 7d 77  7f 10 a4 32 bc 30 d4 82
        0090  bf 40 06 0f 84 32 43 65  67 47 d0 19 59 0e e7 c2
        00a0  d9 c1 10 0a 5e df a2 18  04 86 e5 e4 09 80 99 75
        00b0  fd 21 ad 86 5f 77 ab 5d  aa 79 74 ed eb ba c4 e8
        00c0  f1 fb b2 ae 6a dd 07 5c  cc 3d 93 99 ff 45 e6 f6
        00d0  c6 d6 d3 22 69 c3 43 50  c0 69 e4 7f 3e 73 df 76
        00e0  6f 9d fc 73 ed 54 0b 49  3b 6f c8 99 32 b1 9b d5
        00f0  15 bd 5f 40 07 a2 f2 92  0e 74 2b f2 01 39 52 b0
    Non-root Certificate
    Key Id Hash(rfc-sha1): 8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
    Key Id Hash(sha1): e7 a5 38 8b 64 5e bd 6e ee 7b 3f 61 bb 8a ed 2c cc 4b 2c 2f
    Cert Hash(md5): 69 84 7c 7c d8 2a 35 12 e9 6b e8 6a fd ca be 92
    Cert Hash(sha1): eb 2f 11 1b b0 c2 92 a0 14 74 50 42 50 1e de c5 53 de d7 df
    ----------------  End Nesting Level 1  ----------------
      CERT_MD5_HASH_PROP_ID(4):
        69 84 7c 7c d8 2a 35 12 e9 6b e8 6a fd ca be 92
      CERT_SHA1_HASH_PROP_ID(3):
        eb 2f 11 1b b0 c2 92 a0 14 74 50 42 50 1e de c5 53 de d7 df
      CERT_KEY_IDENTIFIER_PROP_ID(20):
        8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
    Cannot find the certificate and private key for decryption.
    ================ Certificate 1 ================
    ================ Begin Nesting Level 1 ================
    X509 Certificate:
    Version: 3
    Serial Number: 96b6de15a74b97ac
    Signature Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
        Algorithm Parameters:
        05 00
    Issuer:
        CN=xyz QA CA
        O=xyz Technical Resources Ltd
        C=US
    NotBefore: 11/13/2012 3:35 PM
    NotAfter: 11/13/2032 3:35 PM
    Subject:
        CN=xyz QA CA
        O=xyz Technical Resources Ltd
        C=US
    Public Key Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
        Algorithm Parameters:
        05 00
    Public Key Length: 2048 bits
    Public Key: UnusedBits = 0
        0000  30 82 01 0a 02 82 01 01  00 d2 5f 7d c0 c5 25 7f
        0010  2c 4c a2 4a 9b 6f e7 7a  35 cd 9a 2a 88 30 36 9b
        0020  f8 a4 d8 31 64 72 36 1c  1b 2c dc 73 11 d6 57 a2
        0030  97 91 6d bb d0 3c 13 65  28 4d 78 4e e1 c7 06 ac
        0040  16 c1 2a 62 39 ba 39 f9  a1 b9 4a 14 39 28 58 0d
        0050  f4 97 83 d5 ee 45 91 4a  41 06 e5 b9 60 40 20 48
        0060  85 f4 2d 8e 04 7f 81 12  3a 26 e1 0f 21 32 49 bc
        0070  20 ef 12 69 5a 20 a4 51  65 6d 85 4c 0f 4c 91 4c
        0080  26 47 27 a7 9e 49 e0 f7  56 08 fc 90 47 11 6c a9
        0090  b8 81 c6 83 c8 b2 2d e8  c4 ba 8b 45 32 c5 dd a0
        00a0  d9 1c 85 10 d6 6b 42 50  9a 42 d6 e4 51 32 73 59
        00b0  92 5b d1 44 82 dc be 75  65 94 e7 4a 79 15 ed 23
        00c0  f8 a3 3e 28 92 31 75 5c  fa b9 1b 6d e0 c3 d0 24
        00d0  7a 09 86 d0 2d c7 42 eb  6b fc 95 ed 62 13 21 35
        00e0  2f 0e b6 cd c2 c3 66 d4  a6 1b 53 15 49 64 ac 34
        00f0  11 20 8b e4 46 bc 60 68  3e 1b cb 5c b8 05 f4 a8
        0100  0a a3 53 d0 37 2a 2d 73  01 02 03 01 00 01
    Certificate Extensions: 7
        2.5.29.19: Flags = 1(Critical), Length = 5
        Basic Constraints
            Subject Type=CA
            Path Length Constraint=None
        2.5.29.14: Flags = 1(Critical), Length = 16
        Subject Key Identifier
            c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
        2.5.29.15: Flags = 1(Critical), Length = 4
        Key Usage
            Certificate Signing, Off-line CRL Signing, CRL Signing (06)
        2.5.29.35: Flags = 1(Critical), Length = 7e
        Authority Key Identifier
            KeyID=c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
            Certificate Issuer:
                 Directory Address:
                      CN=xyz QA CA
                      O=xyz Technical Resources Ltd
                      C=US
            Certificate SerialNumber=00 96 b6 de 15 a7 4b 97 ac
        2.5.29.31: Flags = 0, Length = 36
        CRL Distribution Points
            [1]CRL Distribution Point
                 Distribution Point Name:
                      Full Name:
                           URL=http://pki.xyzre.qa1/crls/root-ca.crl
        1.3.6.1.5.5.7.1.1: Flags = 0, Length = 37
        Authority Information Access
            [1]Authority Info Access
                 Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
                 Alternative Name:
                      URL=http://pki.xyzre.qa1/root-ca.cer
        2.5.29.32: Flags = 0, Length = 6e
        Certificate Policies
            [1]Certificate Policy:
                 Policy Identifier=2.16.840.1.101.3.2.1.48
                 [1,1]Policy Qualifier Info:
                      Policy Qualifier Id=CPS
                      Qualifier:
                           http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/documents/test_policy.pdf
    Signature Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
        Algorithm Parameters:
        05 00
    Signature: UnusedBits=0
        0000  69 25 3a 36 f1 13 25 88  73 94 eb cf 5b 70 2e 86
        0010  8c 0d 7a 8f 3a 49 0e 42  18 da c9 00 26 68 ea 42
        0020  cd 2a 24 43 0d ec 6b 15  73 14 33 69 c2 60 3d 40
        0030  1c 4d 59 12 7a e9 03 00  81 ba 1e 50 55 05 bd 60
        0040  88 84 bb 8e e3 f5 ce 00  42 ae fd 01 05 fd bc 5f
        0050  af cc e3 a4 4d f2 84 8b  9b 0d 24 16 d6 d4 51 da
        0060  50 9c c4 69 d6 b8 18 be  e5 5c 48 b8 8a a3 d4 22
        0070  0e 26 f2 15 d8 ff 19 34  d4 1d 69 50 02 51 da e8
        0080  ad 05 a3 2f 1c e9 0f da  e3 4c 36 c4 cd 6e a5 76
        0090  88 19 90 78 ad fe 94 62  46 91 2b 0a 36 df e2 ea
        00a0  4a a9 f4 5c dc 77 4d e5  f4 ab e9 b9 da f6 b0 9f
        00b0  6c f5 50 74 14 19 05 df  96 b5 ee af a3 31 a5 af
        00c0  8f 6c be 67 43 78 55 0e  39 46 80 05 12 5f c2 4f
        00d0  24 fc 13 f7 e5 ee 64 0f  dd 9a 49 5c 57 10 1c 4b
        00e0  7a 9f 5a 1f 0c ec 5b 8d  b4 c4 ed d8 09 cc 1c d9
        00f0  9f 04 3f 85 ab 95 48 8e  77 e0 91 81 39 46 fb a3
    Signature matches Public Key
    Root Certificate: Subject matches Issuer
    Key Id Hash(rfc-sha1): c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
    Key Id Hash(sha1): f0 fc 52 1c c1 a6 16 2d 28 c1 71 84 ae d4 18 87 74 c4 f8 1c
    Cert Hash(md5): c9 af 16 63 9e 51 7b 8e 22 25 96 d7 a7 66 fa ab
    Cert Hash(sha1): e6 0b ef c1 fb e6 94 13 dc 9f 26 80 33 31 43 d9 ec af d7 be
    ----------------  End Nesting Level 1  ----------------
      CERT_MD5_HASH_PROP_ID(4):
        c9 af 16 63 9e 51 7b 8e 22 25 96 d7 a7 66 fa ab
      CERT_SHA1_HASH_PROP_ID(3):
        e6 0b ef c1 fb e6 94 13 dc 9f 26 80 33 31 43 d9 ec af d7 be
      CERT_KEY_IDENTIFIER_PROP_ID(20):
        c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
    Cannot find the certificate and private key for decryption.
    ================ Certificate 2 ================
    ================ Begin Nesting Level 1 ================
    X509 Certificate:
    Version: 3
    Serial Number: 1500000003a24d67389af826d7000000000003
    Signature Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.10 RSASSA-PSS
        Algorithm Parameters:
        30 00
    Issuer:
        CN=xyz Issuing CA
    NotBefore: 11/15/2012 3:13 PM
    NotAfter: 11/15/2013 3:13 PM
    Subject:
        [email protected]
        CN=(e) Hugh Kelley
    Public Key Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
        Algorithm Parameters:
        05 00
    Public Key Length: 2048 bits
    Public Key: UnusedBits = 0
        0000  30 82 01 0a 02 82 01 01  00 e4 55 77 34 c0 b7 58
        0010  55 cd 71 1e da d4 83 fd  f4 bd a5 d5 26 52 6c 7e
        0020  8d 74 ea 0a b6 2c 0c ae  b4 8f fc 95 07 9b 1a d4
        0030  e1 9f ed e3 7e d7 f4 f0  04 2c e4 ed 4c 49 2b d7
        0040  b4 42 c0 1c 12 7c b8 76  22 83 e6 d9 44 78 ce 26
        0050  20 5c 9c 71 30 3c 78 01  74 fa ac f9 7b b3 83 28
        0060  a8 18 52 10 d4 a5 f0 29  40 15 40 16 5c 90 4b 5d
        0070  c4 57 9d 3d 29 4e ce 80  b1 f1 ae 17 a4 cc 85 0b
        0080  a2 5e 73 0f ac 0f ff 8b  05 0c b9 f2 17 b3 ad 2f
        0090  b7 33 c7 ac bf 16 0f 09  2a e6 b7 f9 90 42 0b 6f
        00a0  3b 7f df 86 e6 e9 33 b6  d5 2d be 5f 65 4b 87 45
        00b0  d4 53 fc 8e de 0f 49 fd  8b 84 f5 2e cd 00 a9 cd
        00c0  0c b2 e2 7e 3e f9 e3 28  2f 9a 55 85 3e b8 b2 3a
        00d0  89 ce 19 bd 88 b2 74 da  42 ac bf 07 6c 4a b8 2e
        00e0  94 36 3b 28 f0 45 ec 59  f4 22 f3 03 47 85 ef 4c
        00f0  ba f5 24 3e 55 60 8b e8  6e e3 e9 1e bf 3c c9 75
        0100  88 9c 39 6c 20 66 c0 92  85 02 03 01 00 01
    Certificate Extensions: 10
        1.3.6.1.4.1.311.21.7: Flags = 0, Length = 30
        Certificate Template Information
            Template=1.3.6.1.4.1.311.21.8.11609700.13554795.12405411.13975648.10011376.129.8742862.14 66929
            Major Version Number=100
            Minor Version Number=5
        2.5.29.37: Flags = 0, Length = 22
        Enhanced Key Usage
            Client Authentication (1.3.6.1.5.5.7.3.2)
            Secure Email (1.3.6.1.5.5.7.3.4)
            Encrypting File System (1.3.6.1.4.1.311.10.3.4)
        2.5.29.15: Flags = 1(Critical), Length = 4
        Key Usage
            Digital Signature, Key Encipherment (a0)
        1.3.6.1.4.1.311.21.10: Flags = 0, Length = 28
        Application Policies
            [1]Application Certificate Policy:
                 Policy Identifier=Client Authentication
            [2]Application Certificate Policy:
                 Policy Identifier=Secure Email
            [3]Application Certificate Policy:
                 Policy Identifier=Encrypting File System
        1.2.840.113549.1.9.15: Flags = 0, Length = 37
        SMIME Capabilities
            [1]SMIME Capability
                 Object ID=1.2.840.113549.3.2
                 Parameters=02 02 00 80
            [2]SMIME Capability
                 Object ID=1.2.840.113549.3.4
                 Parameters=02 02 00 80
            [3]SMIME Capability
                 Object ID=1.3.14.3.2.7
            [4]SMIME Capability
                 Object ID=1.2.840.113549.3.7
        2.5.29.14: Flags = 0, Length = 16
        Subject Key Identifier
            c2 1d d2 c8 90 64 9c 38 a9 66 9d 12 8b 1a a6 ab a8 72 2a 11
        2.5.29.35: Flags = 0, Length = 18
        Authority Key Identifier
            KeyID=8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
        2.5.29.31: Flags = 0, Length = 44
        CRL Distribution Points
            [1]CRL Distribution Point
                 Distribution Point Name:
                      Full Name:
                           URL=http://pki.xyzre.qa1/crls/xyz Issuing CA.crl
        1.3.6.1.5.5.7.1.1: Flags = 0, Length = 45
        Authority Information Access
            [1]Authority Info Access
                 Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
                 Alternative Name:
                      URL=http://pki.xyzre.qa1/xyz Issuing CA.crt
        2.5.29.17: Flags = 0, Length = 50
        Subject Alternative Name
            Other Name:
                 Principal [email protected]
            RFC822 [email protected]
    Signature Algorithm:
        Algorithm ObjectId: 1.2.840.113549.1.1.10 RSASSA-PSS
        Algorithm Parameters:
        30 00
    Signature: UnusedBits=0
        0000  51 58 a1 89 fc fe 9d b3  67 36 9f 4d 41 75 9e 9f
        0010  b8 30 10 3b c8 f1 0b 6a  b8 ab 84 73 2e 91 7e 05
        0020  e0 3a 5b 34 cd 0a 35 bd  e0 f6 c2 7c 7f d0 d6 b3
        0030  03 3d 8c dd 52 04 7f 62  55 a5 14 a7 5a 20 77 5d
        0040  0f bb f6 4d a3 8c 2e 98  76 39 f4 30 18 bf be 5f
        0050  0c 62 20 40 39 34 e6 de  d2 dd 01 dd e9 bb d0 e5
        0060  1e 93 93 0e de c4 c5 86  9e 15 72 ea 4c 37 5c 6c
        0070  3d dc 69 8d 17 9d f8 b6  2a 51 1f f5 bc f5 fb 58
        0080  2c 03 4f 88 b8 58 a3 cd  ca 38 28 3a c9 34 79 4a
        0090  46 7c de a1 a8 fa 28 34  1f 23 96 69 51 f1 c7 41
        00a0  0b c8 a9 39 71 6c 4f 57  81 7f ec a7 2f 65 b9 97
        00b0  c8 2d 1e 24 ff fc d9 58  5c 07 e9 2c 83 77 64 a9
        00c0  8f 5d 42 9e c3 ea 85 88  39 7b 23 56 38 6d c9 15
        00d0  4c 80 de cf 00 e0 73 27  e2 f1 b3 d4 c9 b5 83 74
        00e0  4f 6e 6f 03 2f df c1 29  24 de 6a 70 cf de d4 1f
        00f0  fb 07 08 85 89 f9 08 f7  68 5c 68 29 2e 3c 6c de
    Non-root Certificate
    Key Id Hash(rfc-sha1): c2 1d d2 c8 90 64 9c 38 a9 66 9d 12 8b 1a a6 ab a8 72 2a 11
    Key Id Hash(sha1): 42 9c bd 63 60 4c d2 a8 55 bd 1b f4 70 25 34 cd 72 38 ca 8c
    Cert Hash(md5): af 8b 1e 76 71 f5 53 f4 93 62 1d e7 5e a8 d1 ff
    Cert Hash(sha1): 4f 3b d3 48 ba 05 65 dd 99 bb 33 65 5b 5e ba 13 28 fe 2d 80
    ----------------  End Nesting Level 1  ----------------
      CERT_MD5_HASH_PROP_ID(4):
        af 8b 1e 76 71 f5 53 f4 93 62 1d e7 5e a8 d1 ff
      CERT_SHA1_HASH_PROP_ID(3):
        4f 3b d3 48 ba 05 65 dd 99 bb 33 65 5b 5e ba 13 28 fe 2d 80
      CERT_KEY_PROV_INFO_PROP_ID(2):
        Key Container = {0136F9BB-2135-4642-827C-B883E0BDAF41}
      Unique container name: 1119ced7dad9cbd7d39924c9f35b5886_f10cfee5-eccc-4ef4-b0fb-7042bc1815c3
        Provider = Microsoft Enhanced Cryptographic Provider v1.0
        ProviderType = 1
        Flags = 0
        KeySpec = 1 -- AT_KEYEXCHANGE
      CERT_CEP_PROP_ID(87):
      Enrollment Policy Url: ldap:
      Enrollment Policy Id: {D8416D24-E050-45B1-B348-B9218292357C}
      Enrollment Server Url: Q-PKI-01.xyzre.qa1\xyz Issuing CA
      Request Id: 3
      Flags = 0
        DefaultNone -- 0
      Url Flags = 20 (32)
        PsfAllowUnTrustedCA -- 20 (32)
      Authentication = 2
        Kerberos -- 2
      Enrollment Server Authentication = 2
        Kerberos -- 2
      CERT_REQUEST_ORIGINATOR_PROP_ID(71):
        Q-APPDEV7-01.xyzre.qa1
      CERT_KEY_IDENTIFIER_PROP_ID(20):
        c2 1d d2 c8 90 64 9c 38 a9 66 9d 12 8b 1a a6 ab a8 72 2a 11
      Unique container name: 1119ced7dad9cbd7d39924c9f35b5886_f10cfee5-eccc-4ef4-b0fb-7042bc1815c3
      PP_KEYSTORAGE = 1
        CRYPT_SEC_DESCR -- 1
      KP_PERMISSIONS = 3f (63)
        CRYPT_ENCRYPT -- 1
        CRYPT_DECRYPT -- 2
        CRYPT_EXPORT -- 4
        CRYPT_READ -- 8
        CRYPT_WRITE -- 10 (16)
        CRYPT_MAC -- 20 (32)
      D:(A;ID;GAGR;;;SY)(A;ID;GAGR;;;BA)(A;ID;GAGR;;;S-1-5-21-2052111302-1708537768-839522115-2 4370)
        Allow Full Control    NT AUTHORITY\SYSTEM
        Allow Full Control    BUILTIN\Administrators
        Allow Full Control    xyzRE\hugh.kelley
    Private Key:
      PRIVATEKEYBLOB
      Version: 2
      aiKeyAlg: 0xa400
        CALG_RSA_KEYX
        Algorithm Class: 0xa000(5) ALG_CLASS_KEY_EXCHANGE
        Algorithm Type: 0x400(2) ALG_TYPE_RSA
        Algorithm Sub-id: 0x0(0) ALG_SID_RSA_ANY
      0000  52 53 41 32                                        RSA2
      0000  ...
      048c
    Encryption test passed
    CertUtil: -dump command completed successfully.

    Hi Hugh,
    As you figured out the certificate was using a signature algorithm that Acrobat did not understand. The "signature algorithm" is a composite of the the digest algorithm (e.g. sha1), and the encryption algorithm (e.g. RSA). Acrobat understands the following digest algorithms; MD5, SHA-1, RIPEMD-160, SHA-256, SHA384, and SHA512. As far as encryption algorithms go, it understands DSA and RSA. Just to make things a little more complicated, version XI also can handle elliptic curve, but versions 6 thru 10 were limited to DSA & RSA. If you are using a digital ID created with the DSA encryption algorithm then the only digest algorithm Acrobat can use with is SHA-1. Just like you saw sha1RSA, you could also use a digital ID with the sha1DSA signature algorithm. If you are using RSA then it will pair with all six digest algorithms I noted above (e.g. sha256RSA).
    The Probabilistic Signature Scheme is not something Acrobat understands at all.
    Steve

  • NESTED Tables for Sub-types when creating table for Super-type

    If I create the following types, as an example:
    Person with subtypes: Employee and Customer
    Appointment
    CREATE OR REPLACE TYPE Person_OT AS OBJECT (
    person#                         NUMBER,
    personSurname                    VARCHAR2(50),
    personForenames               VARCHAR2(50),
    personDateOfBirth               DATE,
    personAddress                    Address_OT,
    ) NOT FINAL ;
    CREATE OR REPLACE TYPE Employee UNDER Person_OT (
    empSalary               NUMBER,
    empNoSales          NUMBER,
    makes               Appointment_List_OT
    ) FINAL ;
    CREATE OR REPLACE TYPE Appointment_OT AS OBJECT (
    some attributes
    CREATE OR REPLACE TYPE Appointment_List_OT AS TABLE OF REF Appointment_OT ;
    When creating the table to hold objects of Person type, how can the requisite nested table for representing 'makes' be declared? The below approach is not correct, however the table will not compile without naming the nested tables.
    CREATE TABLE Person_TBL OF Person_OT (
    Person#     PRIMARY KEY)
    NESTED TABLE makes STORE AS Appointment_List_NTBL;
    Advice very much appreciated!

    CREATE TABLE Person_TBL OF Person_OT(
    Person# PRIMARY KEY)
    NESTED TABLE TREAT(SYS_NC_ROWINFO$ AS EMPLOYEE).MAKES STORE AS Appointment_List_NTBL
    Table created.
    SQL> select * from user_nested_tables
      2  /
    TABLE_NAME                     TABLE_TYPE_OWNER
    TABLE_TYPE_NAME                PARENT_TABLE_NAME
    PARENT_TABLE_COLUMN
    STORAGE_SPEC                   RETURN_TYPE          ELEMENT_SUBSTITUTABLE
    APPOINTMENT_LIST_NTBL          SCOTT
    APPOINTMENT_LIST_OT            PERSON_TBL
    TREAT(SYS_NC_ROWINFO$ AS "SCOTT"."EMPLOYEE")."MAKES"
                           DEFAULT                VALUE                         N
    SQL>  SY.

  • Set default value for price unit when creating material master data

    HI: Every
    could you tell me how to use user-exit or else ways to set default value(such as 1000) for field "Price unit" (MBEW-PEINH) when creating material master data(MM01)?
    I have try to use Exit:EXIT_SAPLMGMU_001. However, this way cannot respones it.
    thanks
    Henry

    Hi: Ihave find out a solution
    Use BADI: BADI_MATERIAL_REF
    SPROlogistics general enhancement supplement or change default data (industry)
    And then creating a Implementation Name
    Double click method: CREATE_MATERIAL
    And then write code as below:
    method IF_EX_MATERIAL_REFERENCE~CREATE_MATERIAL.
              c_mbew-peinh = '1000' .
    endmethod.
    However, SAP still store '1000' in database evenif we change the default value such as 100 when we use TCode MM01.
    in additional, we still use MM02 to change the default value such as '100'
    can anybody tell me how to do?
    thanks
    Henry

  • Ask for a certificate when record a script in openscript

    Hi,
    I have an error message when make a playback and I think the reason for that is the following:
    In the Windows browser I have installed a certificate for the application under test and don’t ask me for him. But when I record the script in openscript the browser ask me for the certificate.
    The error message in playback is HTTP response code: 401
    Any suggestion?
    thanks,
    Daniel

    Daniel
    I guess that the application is using client side authentication, if so you need to give the certificate to OpenScript
    View -> OpenScript Preferences -> Record -> HTTP under General settings you can add your certificate.
    Regards
    Alex

  • How to generate an id for a vendor when create a new one?

    Dear friends,
    How to generate a new id for a new vendor when create the new vendor?
    Thanks a lot!

    >
    Qiwei Yin wrote:
    > Dear friends,
    >
    > How to generate a new id for a new vendor when create the new vendor?
    >
    > Thanks a lot!
    Hi,
    For many account groups, there is no need to specify vendor number while creating a new vendor. They will take internal number assignment and you can leave this field blank.
    For external number assignment, you can assign you own number.
    If you are creating vendors through program, and you want your vendors in a particular format, you can use your own number ranges created through SNRO.
    regards
    Sreenivas

  • Organization selection popup when creating new prospect

    Hello,
    When I create a new prospect and go to the opportunity tab and create new opportunity I get an error because organization has not been selected.  Now instead of creating an opportunity from prospect->opportunity tab if i go to Opportunity screen and create a new opportunity for the same prospect then I get a popup for organization selection.  How can I get the same behavior on both opportunity pages?  This is a bug and I dont know if there are any oss notes out there.
    Thank you,
    AP

    Hi AP,
    Glad to hear that the issue is resolved. It looks like you forgot to add the points, :-).
    Best Regards, Adil

  • Can I do a "select all" when creating themes and settings?

    When I am creating my dvd, can I do something so that each of the scene selection screens will have the same theme, same movie clip in the drop zone and same music playing? Is there a way to select all the same preferences for the customize option? Thank you!

    Hi Navy91,
    After you have finished customised the first scene selection menu screen, use the Adanced > Apply Theme To Folders menu command to apply the same theme settings to all other scene selection menus following it.

  • Get new value for LIKP-LGTOR when creating a delivery

    Hello all ,
    when I creating an delivery, I use MIGO or FM BAPI_GOODSMVT_CREATE, I want to update field LIKP-LGTOR.
    To do this , I have created a Z-table which contain WERKS KOSTL(KEY) and LGTOR. so , if we know WERKS & KOSTL we could find LGTOR , and update it.
    The problem is that I cannot find a suitable user exit or BADI to achieve this.
    In BADI LE_SHP_DELIVERY_PROC, I notice that method FILL_DELIVERY_HEADER contain LIKP-WERKS LIPS-KOSTL and we can change LIKP-LGTOR as well, but when debugging , I found that the import data LIKP LIPS are all blank.
    so I want to know if there is some way we could achieve this ?
    Thanks in advance for your replies!
    Kevin

    Hi,
    Even through BADI, you will get LIKP information in CS_LIKP structure in method (FILL_DELIVERY_HEADER).  But you will
    not get both LIKP and LIPS information in same method.  You have use FILL_DELIVERY_ITEM to get LIPS information.
    Regards
    Vinod

  • Photo's disappear from select panel when creating a book (version 7.1.1.)

    Hi,
    If I sort all photo's on date, and look in my photo library, I do not get the same photo's when I switch to the project panel to create a book. The photo-select window above the book lay-out window, only shows a part (all be it a large part) of my complete photo library. Does anyone know how to 'force' iPhoto to show all photo's form the Library in the photo select window?
    Thanks!
    Paul Harts

    The photos in the thumbnails across the top when you are creating a book are ONLY the ones you have placed there - either by having them selected when you created the book project or by dragging them to the book project. The only way to "force" iPhoto to display all of your library is to select all of your library and drag it to the book project - which I personally would find impossible to work with
    LN
    Message was edited by: LarryHN

  • Looking for best practices when creating DNS reverse zones for DHCP

    Hello,
    We are migrating from ISC DHCP to Microsoft DHCP. We would like the DHCP server to automatically update DNS A and PTR records for computers when they get an IP. The question is, what is the best practice for creating the reverse look up zones in DNS? Here
    is an example:
    10.0.1.0/23
    This would give out IPs from 10.0.1.1-10.0.2.254. So with this in mind, do we then create the following reverse DNS zones?:
    1.0.10.in-addr.arpa AND 2.0.10.in-addr.arpa
    OR do we only create:
    0.10.in-addr.arpa And both 10.0.1 and 10.0.2 addresses will get stuffed into those zones.
    Or is there an even better way that I haven't thought about? Thanks in advance.

    Hi,
    Base on your description, creating two reverse DNS zones 1.0.10.in-addr.arpa and 2.0.10.in-addr.arpa, or creating one reverse DNS zone 0.10.in-addr.arpa, both methods are all right.
    Best Regards,
    Tina

  • Cannot select vendor when creating new DC

    Hi all,
    I'm using NWDI, version is 7.14.
    When I try to create a new DC the vendor dropdown is disabled and all I see is sap.com (see snapshot - http://img390.imageshack.us/my.php?image=newprojectjq3.jpg).
    I have opened several projects in the past with no problem (and I could choose my own vendor, the one I created in the SLD).
    How can I solve this?
    Thanks,
    Omri

    Hi Pascal,
    I don't see any errors in the NWDS log file:
    !SESSION נוב 17, 2008 11:07:54.359 -
    java.version=1.4.2_09
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL
    Command-line arguments: -os win32 -ws win32 -arch x86 -feature com.sap.java.ide C:\j2sdk1.4.2_09\bin\javaw.exe
    -Xmx512m
    -Xms128m
    -XX:PermSize=32m
    -XX:MaxPermSize=128m
    -DallUserDir='C:\Documents and Settings\All Users\Application Data'
    -cp C:\Program Files\SAP\IDE\IDE70\eclipse\SapStartup.jar com.sap.ide.eclipse.startup.Main
    -os win32
    -ws win32
    -arch x86
    -feature com.sap.java.ide
    -showsplash C:\Program Files\SAP\IDE\IDE70\eclipse\SapIde.exe -showsplash 600  -data C:\Documents and Settings\mmm\Documents\SAP\workspace -install file:C:/Program Files/SAP/IDE/IDE70/eclipse/
    !ENTRY Startup 1 0 נוב 17, 2008 11:07:54.359
    !MESSAGE Sap NetWeaver Developer Studio - Build: 200711102147
    Under http://<server>:<port>/dtr/system-tools/administration/NameServerConfiguration I see the following URL: http://<server>:<port>/sld/cimom with nwdi admin user and password and 'TrustedCAs' as 'Trusted Store'. I only have entries under the 1st name server (the 2nd is empty).
    When I navigate to http://<server>:<port>/sld/cimom I get 'This is the location of the SLD CIM Object Manager that processes WBEM requests (CIM operations over HTTP).'
    When I check the name server prefix 'haifa.ac.il/hu' in the SLD the 'Disable this SLD as Name Server for NWDI' button is active...
    Regards,
    Omri

  • Exit for VF01/VF02 when creating or changing billing document

    Hi,
    Can any one tell me which exit is triggered when we are creating or changing billing document
    (VF01/VF02).I alreay find the exits but not able to find the exact one.
    Thanks in Advance,
    regards,
    kishore.

    Hi
    Check This EXIT  available for VF01/VF02 And find Exact one
    SDVFX007 User exit: Billing plan during transfer to Accounting
    SDVFX008 User exit: Processing of transfer structures SD-FI
    SDVFX009 Billing doc. processing KIDONO (payment reference number)
    SDVFX010 User exit item table for the customer lines
    SDVFX011 Userexit for the komkcv- and kompcv-structures
    V05I0001 User exits for billing index
    V05N0001 User Exits for Printing Billing Docs. using POR Procedure
    V60A0001 Customer functions in the billing document
    V60P0001 Data provision for additional fields for display in lists
    V61A0001 Customer enhancement: Pricing
    Ranga

Maybe you are looking for