Extension Builder Certificate

What does it take to create a vaild .P12 certificate for Flash Builder to use when running Adobe Extension Manager. I have a SSL cert file but it is not a .P12 file.
Thanks

Some people have suggested ensuring that the certicate is placed in the "login" keychain and that Trust is set to "Always Trust". This worked for some people, but it didn't work for me on Mac OS Leopard.

Similar Messages

  • Need HELP getting my signed certificate to be recognized by Extension Builder in Eclipse! Getting Error in Windows!

    When I use Extension Builder 3 in Eclipse to package my files into a .zxp ... I get an 'invalid certificate' error.  Working in Windows, with Photoshop CC 2014.
    This .p12 certificate does currently work find in Configurator 4 for my CS6 panels.
    Please help me get this working! Thank you!

    Hi hdbrew,
    "extension doesn't contain a valid signature" is a warning message that I've got in the past when Adobe Extension Manager (AEM) wasn't up to date - so you might check whether you've the latest version here: https://creative.adobe.com/en/products/extension-manager.
    Paid vs. Free (self signed) certificates: I had a paid one in the past (no AEM warnings) but there are a couple of shortcomings IMHO:
    1. With Adobe Add-ons, AEM and its warning alerts are bypassed altogether (files are deployed via the CC app) - so from the user point of view there's no difference between self-signed and paid certificates.
    2. An extension signed with a paid certificate stops working when the certificate expires. Self signed ones keep working even past the expiration date.
    And three, I find it "peculiar" to pay a third party authority to certificate Adobe that I am who I am in order to be allowed to developed for... Adobe itself (lot of words to say: free is cheaper ).
    Extension Builder for bundling: as I wrote, personally I don't use EB - it's not been updated in a while (it's been acknowledged by the EB team too - who has kept releasing updates as CEP libraries) and I prefer a simple code editor + command line for signing and packaging, so others can be more helpful than me.
    Yet, if you don't need to package an hybrid extension, it's a matter of a simple line, such as:
    ./ZXPSignCmd -sign yourSourceFolder yourDestFolder/yourExtensionName.zxp yourCertFile.p12 yourCertPassword -tsa https://timestamp.geotrust.com/tsa
    Conversely, if you need to go hybrid (i.e. to deploy extra stuff alongside with your extension, e.g. a plugin) it's a matter of compiling an MXI file and the whole process is slightly more complex. Anyway, you can find information in the blogpost I mentioned earlier (the full series of 16 Tips so far is here).
    Regards,
    Davide Barranca
    www.davidebarranca.com
    www.cs-extensions.com

  • Windows 7 - No Safari Developer Certificate message in Extension Builder

    I have acquired and installed developer certificate for Safari 5 as per instructions provided along the way.
    But when i open Extension Builder, a red message appears on top saying "No Safari Developer Certificate"
    And it also keeps Install and Build Package buttons disabled thus i am unable to do much with Extension Builder.
    Guys need workaround for this rather quickly, thanks for your help.

    Some people have suggested ensuring that the certicate is placed in the "login" keychain and that Trust is set to "Always Trust". This worked for some people, but it didn't work for me on Mac OS Leopard.

  • Adobe Extension Builder signing error.

    We are trying to sign our own plugin for adobe indesign and we have a valid Comodo certificate but seems like it keeps showing a warning everytime is installed in the extensión manager of any computer. We have searched for different solutions but none seems to be working. Which steps should we follow to make sure it Works.
    Thanks,
    Cesar.

    Thanks Fraser.
    I'm signing with Extension Builder with Eclipse (Flash Builder)
    I'm installing with Extension Manager CS6. With Extensión Manager CC occurs the same problem.
    Here a screenshot of the error we get.
    Thanks!
    Cesar.

  • Get Adobe Extension Signing Certificate

    Hello,
    I am a Creative Cloud member and have been working on developing an Extension for InDesign and InCopy versions CS 5.x and above. We are intending to extend the support for other Adobe products also at a later date. Until now, I have been signing the zxp file with a certificate that I created via ExtensionBuilder, but now, we are getting ready to ship the extension to some of our prospective customers as a beta version for some feedback. And for that I need to get the extension signed with a certificate by a recognized authority, so that user does not get an error looking message while installing the extension.
    I did look around a little on Adobe forums and google but could not get a concrete list or steps to do so. What I need to know is:
    1. what all kinds of certificates are available,
    2. how to choose which one I should go for,
    3. how to get the certificate,
    4. certificate's validity (number of uses / time period) and
    5. the cost involved.
    I believe the process of signing the extension will be the same (I am using ant script to build and sign the zxp); please correct me if I am wrong.
    Any help is much appreciated.
    - Swati.

    I was kind of stuck on this one. We need to dispatch the extension to the customers for feedback. I have been searching online for a clue but no luck.
    Any help will be much appreciated.
    Does Adobe give out extension signing certificate? If not, any preferences?

  • Extension signing certificate issues

    I'm having problems with my current certificate issuer (Globalsign) as they decided not to support developers any more and have to change to another company; this means my certificate can't be renewed.
    My knowledge about certificates is very limited, please can you help me?
    Extensions released with the old certificate can still be installed after it expires ? If, yes, will the user become a warning or something else ?
    Some users reported ( before the related certificate issue) that they got "invalid signature" warnings (mainly with CC) and they had to disable internet access in the extension manager to get it installed, this makes me think about the whole system.
    Is really a certificate needed ? Why not just allow us to input our contact details and let the user decide to trust or not?
    Just paying a yearly fee only to guarantee that our names appear at the installation seems not to be very reliable. May be Adobe can allow extension builder developers an easier way to sign our extensions.
    Btw, I assume I'm not the only one signing the extensions, right ?
    Thanks for any help.

    I was kind of stuck on this one. We need to dispatch the extension to the customers for feedback. I have been searching online for a clue but no luck.
    Any help will be much appreciated.
    Does Adobe give out extension signing certificate? If not, any preferences?

  • Why does extension loader check extension's certificate during each loading?

    Hello,
    We are having some problems with an expired code signing certificate.
    We sell a commercial extension which is signed with our code signing certificate. Recently our certificate expired, and we started to receive reports that our extension had stopped working in CS5.
    It looks like CS5 checks the extension's certificate not only during installation, but also at each loading.
    This behavior looks like a serious bug in Creative Suite extension loader since all certificates will expire sooner or later, and this means that all extensions are doomed to stop working at some point, unless they are timely updated.
    Why does CS5 check the certificate at each start up? This doesn't make sense at all, certificates are only used to check that the code is authentic during installation. An authentic extension cannot turn into malware after installation, so there is absolutely no point in checking the certificate after installation.
    Can someone from the CS SDK team comment on this issue? This turned into a major problem for us.
    Thank you in advance,
    Anatoly Paraev
    PixelNovel 

    Anatoly, let me summarise my thoughts/findings on this:
    - Your extension's signature is invalid now that your certificate has expired (as you have reported)
    - Your extension's signature is not timestamped with a timestamp certificate. A signature without a timestamp is only valid till the signing certificate expires. A signature with a timestamp is valid until the timestamp certificate expires, typically a much longer period.
         - As you can infer from this, Extension Builder does not create timestamped signatures and does not give any warning about this. Apologies that we failed to anticipate this problem during CS SDK and Extension Builder development. You will probably agree this is not good enough, and I have filed a bug (#2916071) to ensure this is dealt with in future releases.
    As I mentioned earlier, extension signature validation is performed on extension load to ensure an extension's footprint has not been maliciously modified since installation. I think it is very unlikely that we can remove this signature validation for security reasons, nonetheless I've started a conversation about it internally and can let you know the outcome.
    To help your users now, I think you will need re-sign and re-deploy your extension with a new certificate. So you can timestamp the signature, use ucf.jar in the Packaging and Signing Toolkitto sign the extension rather than Extension Builder. Pass the argument -tsa=<your_chosen_timestamp_server> to ucf.jar when signing and check the signature is timestamped

  • Photoshop cc 2014 with Extension Builder 3 not working properly.

    I can't get even the most basic panel to work in CC 2014. I have created a Default Extension Builder project in eclipse. I then follow this instructions Adobe Extension Builder and Creative Cloud 2014, but when I try to debug it, it doesn't work. The panel shows up (with nothing in it) but says "Cannot complete command because the extension could not be loaded."
    I have created an extension for CC, then changing everything according to the link above, tried to start it in CC 2014 I get the same error, even though it worked in CC.
    Does anyone know how I can fix this problem or what is causing it?
    If not, could anyone provide me with an empty panel project made in Extension Builder that works for you, so that I can maybe figure out what the differences are.
    Regards,
    Mattias

    I think so, yo, only add the PlayerDebugMode like this right?
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
      <key>SmsManifestBaseURL</key>
      <string>http://serviceupdates.adobe.com/CEP4/SmsManifest.xml</string>
      <key>SmsUpdateCheckInterval</key>
      <string>7200</string>
      <key>LogLevel</key>
      <string>1</string>
      <key>PlayerDebugMode</key>
      <string>1</string>
    </dict>
    </plist>
    In this file /Users/<username>/Library/Preferences/com.adobe.CSXS.5.plist
    As you can see I am on a mac.
    Thanks for the help,
    Mattias

  • Having a problem with Flash Builder and Extension Builder - images not apearing on Mac system

    Have a panel created in Flash Builder 4.5 with Extension Builder 2.1. Everything is fine when installed on a PC but when installed on a Mac the images in the panel do not show.
    Mac and PC both using Adobe Photoshop CC . Both installed from same .ZXP file using Adobe Extension Manager CC.
    Any ideas?

    No I used relative path - the path is  images/image name
    example images/cRight.png
    tried downloading Extension Builder 2.1 and compiling on Mac but still have same results - images show up fine in design window , but not when running panel in Photoshop
    Created a new project: testImage
    added an image component to form
    answered yes to add asset to project
    ran project
    image did not show up in Photoshop
    went back to project
    checked item Embed under Common image properties
    ran project and image shows up
    Looks like it works if I add @Embed("assets/image name") on Mac to display images
    tried in my real project:
    Looks like it works if I add @Embed("images/image name") on Mac to display images
    When I change this on PC to @Embed("images/image name") images do not show Up
    Don't know if I need to create two versions one for Mac one for PC
    Don't know how this would affect product on Adobe Exchange

  • Flash Builder 4.7 with Extension Builder 2.1

    A have license of Creative Cloud but in Flash Builder 4.7 the Extension Builder 2.1 wont work, in install say to me this "Adobe Extension Builder 2.1 includes Flash Builder 4.6", see image:
    A pay for 4 Creative Cloud license and 4 Extension Builder license for my team and just anybody work...
    All is using Windows 7, Creative Cloud (updated) and Extension Builder 2.1. I see Extension Builder create folder for Flash Builder 4.6 but just don't work, i search in forum and don't have solution, some guys seeing work installing 4.6, in Creative Cloud don't have Flash Builder 4.6 for download like is in Photoshop, see:
    If just add this combo in Flash Builder with option of download 4.6 working for Creative Cloud fix this problem.

    So, i try this and more...
    1° Download my version:
    2° CleanUp all registry for "Extension Builder", "ExtensionBuilder", "Extension_Builder", "Flash Builder", "FlashBuilder" and "Flash_Builder", after this, CCleaner...
    3° Install, error:
    4° Link file? Interesting, look in depth... Try install manually:
    5° Works, now install Extension Builder 2.1 and... Error! Look the guy "link file" here, is name of a class in *.as too big, why you do this adobe! O_O
    6° Ok, maybe work, because i never use this classes, so look more if i have serial number, oh! I Have serial number for my Extension Builder 2.1! @_@
    7° A light at the end of the tunnel! Insert in Flash Builder and...
    You just fu** kidding of me...

  • What is the replacement for design view in in flex builder 4.7 for cs extension builder?

    Because design view is not available in flash builder than what is the use of extension builder in UI designing now we have to do design UI with xml which is very time consuming and boring  if there is any replacemnt for it than please help me .1 more thing i want to know is that when i make new default project in extension builder(flash builder 4.6) than it also not able to load design mode errror is
    C:\Program Files\Adobe\Adobe Flash Builder 4.6\eclipse\plugins\com.adobe.cside.libsinstaller_2.0.0.4-33034\archive\cslibs\2.0\4.5\re lease\apedelta.swc- not respondingSWC file failed to load. Any component dependent on this SWC file will not be displayed in the Design Mode.The SWC may have failed to load because of:
    *  Incompatible definitions caused by usage of a different SDK version
    *  Missing referred class definitions

    I have researched this quite considerably and my understanding is that Adobe have no intention of supporting Design View any more for Extension Builder.  In my opinion a very disappointing decision and one that is hard to comprehend.
    The best workaround I can find is to create the majority of your design in a parallel, non Extension Builder, project and then convert/import your design into your Extension.  This is by no means as satisfactory as having Design View for the Extension you are writing but it is better than simply creating your layout by guess work/trial and error.
    Although this has not been announced by Adobe, I have a suspicion that the reason they have decided not to put any further resources into fixing Design View is that Extension Builder as we know it is going to be abandoned soon, probably replaced with an HTML5/JavaScript method of building extensions.  My concern with this is that, other than wanting reassurances that there will be backward compatibility support for old extensions, There will not be a way of compiling an extension in a way that prevents people from seeing your code.
    This is all speculation and I guess we will have to wait and see what happens.  Hope this has helped.

  • Adobe Creative Suite Extension builder 2 not supported in Flash Builder 4.7 64 bit

    Couldn't find anywhere to submit a bug report so hopefully this is a good place.
    I was able to succesfully download and install the Adobe Creative Suite Extension builder 2 into Flash Builder 4.7 with not problems.
    When I click File -> New -> Creative Suite Exention Project nothing happends. I recieve no error messages just the Project wizard panel that is expected to open doesn't open.
    The extension works as expected when installed into the non-beta Flash Builder 4.6 32 bit verison.
    I suspect there may be an incompatibility when switching to the 64 bit version of Flash Builder.

    Hi everyone,
    The problem is that Flash Builder 4.7 is not compatible with Extension Builder 2. Therefore we have provided Flash Builder 4.6 available for download, see links below.
    We apologise for any inconvenience caused. Please don't hesitate to contact me if you run into further problems.
    Best regards,
    Hallgrimur
    Product Manager - Extension Builder
    Links:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5517(Windows)
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5516(Mac)

  • Extension Builder 2.1 in Flash Builder 4.7

    It is possible to give an estimate of when we will have a version of the Extension Builder compatible with version 4.7 of Flash Builder?

    Hi WebystherFaria,
    Have you been able to use CS Extension Builder 2.1 SDK with Flash Builder 4.7 or not?

  • How do I install and build and extension with extension builder 2.1?

    Honestly, I am beyond frustrated right now.
    1. Extension Builder 3 - This will only install and run with Eclipse. JRE 1.7.
    This only allows me to use Extendscript to write scripts with. Extendscript is so frustrating to use. It seems like there are a lot of missing properties for working with color models in illustrator. The documentation is also terrible for Extendscript. Something that seems like it would be simple to do like export an RGB JPEG is impossible to spec out in the EXPORT JPEG settings. Its also impossible to set the color space of a NEW AI document unless you use the add(); instead of addDocument(); There are conflicting incomplete properties of both methods. If you use one, one set of settings is missing if you use the other another set is missing... WHAT IS SOMEONE SUPPOSED TO DO???
    2. Flash Builder 4.7 will not run Extension Builder 3.
    3. I bought Extension Builder 2.1 which is supposed to install Flash Builder 4.6, but the installation keeps failing right at the end. This apparently also requires that you use JRE 1.6 which is not compatible with Mavericks.
    This all seems impossible... how in the heck are people learning how to do build extensions, its a surprise that any exist at all. If they do They are likely not building them with the Adobe tools. I know enough about code to be dangerous but don't have a doctorate in troubleshooting all of these compatibility, and documentation issues.
    All I want to do is write an extension, or a script that allows me to
    1. copy the art from two layers.
    2. color the background of the AI document to the background color of the original document
    3. resize art from both layers to fit on a 216 x 216 pixel square.
    4. Save the document as a: JPEG - ANTI-ALIAS SUPER SAMPLED - 150 DPI - RGB - MEDIUM QUALITY - CLIP TO ARTBOARD - WITH THE SAME NAME AS THE ORIGINAL FILE
    I AM AT MY WITS END WITH THIS WHOLE PROCESS. I AM ABOUT TO GIVE UP UNLESS SOMEONE CAN HELP GIVE ME A LITTLE INSIGHT.

    Hi,
    First of all, remember that Extension Builder 2.1 only supports building Flash based extensions which have been phased out. If you are building extensions for Creative Cloud and beyond, you should use HTML5. See more info here: Introducing HTML5 extensions | Adobe Developer Connection
    The installation is probably failing because you have some leftovers from a previous installation. The installer will detect if you have Flash Builder 4.5 or Flash Builder 4.6 installed (NOT Flash Builder 4.7). If it finds that you have Flash Builder 4.5/4.6 installed, it will attempt to install the plugin on top of it. If it does not detect Flash Builder 4.5/4.6, it will install Flash Builder 4.6 Premium.
    I highly recommend you look into the new HTML5 extensibility. Here you can find tons of resources: Adobe CEP Resources by Adobe-CEP
    Best regards,
    Hallgrimur

  • FYI: Extension Builder project w/ LCDS: channel-definition endpoint having context.root

    This is an FYI of an issue and its workaround.
    If developing a CS SDK Extension in Flash Builder / Extension Builder and the project is configured to use LCDS (LiveCycle DataServices), then if your services-config.xml contains Channel definitions having the variable {context.root} in the endpoint URL, then the following error will occur.  This will happen even if you are not using that Channel in your Destination channel list.
    The services-config.xml laid down when using LCDS integrated into ColdFusion has by default some channel definitions using context.root in the endpoint URLs.   This is how I encountered the issue.  On the other hand, the free developer edition of LCDS on Tomcat puts down a services-config.xml that does not have any reference to {context.root} in channel definitions, so the problem will not be encountered there.
    Since I was not using a context root (was using the default of just "/"), I commented out the offending channels in services-config.xml to resolve the issue.  One could also leave the (unused) channel definitions and then remove the {context.root} part from the endpoint.
    ERROR
    The services configuration includes a channel-definition 'java-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
    CHANNEL DEFINITION
    <!--  Java Based Endpoints -->
            <channel-definition id="java-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
            </channel-definition>

    Make sure your context root is defined in the project properties.  This is at "project/properties/Flex Server" from the menubar or package explorer context menu.  Alternately, you can hardcode your context root in the services-config.xml file/channel definition.

Maybe you are looking for