I am looking for the Mime type for an aetx file.
This file is used when distributing a windows phone 8 application in house. a user downloads and installs this to their phone.
But, when you download this file the phone does not give the option to install this enrollment token.
I can only guess the web server is not set to the correct MIME type so the phone is responding appropriately.
my google skills have failed me on the occasion and the microsoft documentation is... sparse on this subject.
thanks for any help.
Martyn
Finally found it. in the aet.xml file that's created when you generate one of these tokens you can see its an x509 certificate file.
So, the mime type is:
"application/c-x509-ca-cert"
So you can host this on a secure site and then set the mime type for your users to download, hopefully it saves someone else some time.
While Martin's answer is correct for Windows Phone 8.0, it won't work for Windows Phone 8.1.
If you use "application/c-x509-ca-cert" with 8.1, the .aetx file is transformed to .cer and you get the error 0x8028a001 "Your phone couldn't add one or more certificates because the certificate file might be unsupported or corrupt ...".
The correct type for 8.1 is "application/octet-stream". Same mime-type used when you send the token as attachment in an email.
But with "application/octet-stream", WindowPhone 8.0 doesn't see the aetx file as token and displays its content to the user.
The solution is to use a servlet (or equivalent if you're not using java) to set the mime type dynamically.
Related
The passTypeIdentifier or teamIdentifier provided may not match your certificate, or the certificate trust chain could not be verified.
I am creating new Pass type ID in apple developer account using my pass type ID but, I was created pass type ID after I also create certificate then install in keychain,
Now, I export 2 file and save .p12 file at my folder, after that I open terminal and extract with .p12 file to .pem file and upload to my AWS server
Now, I run this code and try to download in iPhone safari browser but not able to download it.
After I try to debug via Xcode using Console and I figure out like
The passTypeIdentifier or teamIdentifier provided may not match your certificate, or the certificate trust chain could not be verified.
I am creating a website that have a link to download my chrome CRX app to install it on chrome, the problem is whenever I try to download it it's give me an error that says: " Package is invalid: 'CRX_REQUESTED_PROOF_MISSING' ".
How can I fix this problem?
NOTE: my app is working when I install it using developer tools.
My manifest.json:
{"name":"MY_APP_NAME",
"version":"0.0.1",
"manifest_version":2,
"minimum_chrome_version":"37.0.0.0",
"permissions":["webview","power","storage","videoCapture","geolocation","pointerLock","system.display",{"fileSystem":["write","retainEntries","directory"]},"accessibilityFeatures.read","accessibilityFeatures.modify"],"app":{"background":{"scripts":["js/foam.js","js/cab.js","config.js","background_main.js"]}},
"default_locale":"en",
"icons":{"128":"img/128.png"}}
I'm also currently having this issue and trying to find workarounds for it. Unfortunately it seems that due to Chrome's security policy, plugins needs to go through their webstore in order to have the multiple levels of "proof" before chrome will accept it as a legit extension. So far it seems the only way to get it to work is to load it as an unpacked extension, go through the webstore, or force install it via group policy.
Links and refs:
https://developer.chrome.com/apps/external_extensions
https://support.google.com/chrome/a/answer/6306504?hl=en
https://github.com/oncletom/crx/issues/109
According to documentation, Chrome does not allow installing CRX from outside of their store, unless in developer mode or through enterprise policy: https://developer.chrome.com/extensions/hosting_changes, or on Linux (it's mentioned at the beginning of linux_hosting i linked in my previous comment).
So that may be a reason, because in their source, that "proof missing" error is returned only if either public key is missing, or "required key" is missing:
https://github.com/chromium/chromium/blob/c48c9b176af94f7ec65e20f21594524526d2a830/components/crx_file/crx_verifier.cc#L178
"required key" seems to be their predefined key:
https://github.com/chromium/chromium/blob/c48c9b176af94f7ec65e20f21594524526d2a830/components/crx_file/crx_verifier.cc#L134
and
https://github.com/chromium/chromium/blob/c48c9b176af94f7ec65e20f21594524526d2a830/components/crx_file/crx_verifier.cc#L42
I'm guessing that's the public part of Chrome Web Store key? There's no easy or even "practical" way to create signature that will match their key.
So, either it's the missing Chrome Web Signature key, or something is wrong with how we create signature using developer's key.
How can I distribute my extension if I cannot upload it to the Chrome Web Store for policy reasons?
These changes are effective only on Windows stable and beta channel. Users who want to get extensions that are not hosted on the Chrome Web Store can do so on Chrome dev/canary channels in Windows or on all Chrome channels in other operating systems.
What are the supported deployment options for extensions after this change?
Apart from users installing extensions from the Chrome Web Store, the following deployment options will be supported:
For OSX and Linux, extensions can be installed via a preferences JSON file.
For Windows, extensions can be installed via the Windows registry. In the Windows registry, ensure that the update_url registry key points to the following URL: https://clients2.google.com/service/update2/crx. Local .crx installs via the path registry key are deprecated. Note that this deployment option works only for Chrome Web Store hosted extensions, and update_url cannot point to any other host other than https://clients2.google.com/service/update2/crx.
For Enterprises, we’ll continue to support group policy to install extensions, irrespective of where the extensions are hosted. Note that the user's machine has to join a domain for GPO policy pushes to be effective.
I have signed an Adobe AIR desktop app using a Cocomo Certificate. When I install on a Mac, the publisher is UNKNOWN. But the same .air file sent to a windows user is OK and installs as any signed app should.
Why should this happen? A certificate working on one OS, but not the other?
How can I investigate further? - to determine the cause.
Here are some more details:
The Certificate was obtained by a colleague on their PC. They converted it to a .pfx file, and sent me the .pfx, along with the password they used. I built the signed air app on my Mac.
My guess is: in addition to the main .p12/.pfx key for the AIR build process, you should try to use Mac Ceritificate (Developer ID Application: http://c2n.me/3qcrChL.png ). It helped me. The certificate might be got on the Apple Developers website: https://developer.apple.com (if you have a subscription).
In my case I was able to install .dmg on my MacBook Pro (where the .dmg file was created), but other users weren't able to install (when I send the file through the Internet or Skype).
Actually, the very process of signing is not clear. In my case I had to go through few steps:
1) Create .dmg (regular Adobe AIR build)
2) Deploy it
3) Sign the folder inside of it, something like dmg-folder-name/Contents/Resources/application-filename/Contents/MacOS/application-filename (where "dmg-folder-name" is sort of combination of the filename of the application + ".app", "application-name" is the filename of your application)
4) Sign the folder dmg-folder-name/Contents/MacOS/dmg-volume-name (where "dmg-volume-name" is something like "Install " + the filename of the application)
5) Sign the main dmg-folder
6) Create the new .dmg based on the signed files
It took a lot of time for me to figure out the correct solution. Also, please, pay attention to the order of steps, because it's IMPORTANT to sign the content of the main folder before you sign the main dmg-folder!
Also, I was able to find the topic on the Adobe website: https://forums.adobe.com/thread/1470113 . It has a lot of suggestions and some of them don't workd in my case, but some of them helped me to find a solution.
I have just installed Vault on my machine, I intend touse it single user.
When trying to use it for the first time, I get the error message below.
Is there anything I should enable?
I have the correct passwords.
I am using the Admin account.
I have Windows * 64 bits, Vault is also 64 bits.
Thanks to Beth's answer below, now I can at least visualise the following page, but still not be able to follow the links in it.
This is the result I get when I click on the links(Picture below).
Error messages are below, but the formatting is not good.
Most likely causes: The request matched a wildcard mime map.
The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different handler.
Things you can try: If you want to serve this content as a static file, add an explicit MIME map.
Detailed Error Information: Module StaticFileModule Notification ExecuteRequestHandler Handler StaticFile Error Code 0x80070032
Requested URL http://vrindavana:80/VaultService/Admin/default.aspx Physical Path C:\inetpub\wwwroot\VaultService\Admin\default.aspx
Logon Method Anonymous
Logon User Anonymous
IIS:
I have IIS installed and if I browse it I see what's on the picture below.
First try reaching the Vault server using a browser. Try the URL http://<your Vault server name>/vaultservice/index.html. If you can not reach that page, then change to either the FQDN or the IP address.
If you still cannot reach the index.html page, then try reaching it using a browser right on the server and use localhost. The URL would then be http://localhost/vaultservice/index.html.
Let me know the results of these URLs first and then I'll give you next steps.
Beth
SourceGear Technical Support
Thanks for the update.
The error seems to indicate a problem with the .NET Framework. Here are the next steps you should try.
1) Register the .NET framework with IIS. Run a command-prompt as administrator and then change directories until you get to the highest version of the 4.x .NET framework. It might look something like cd C:\Windows\Microsoft.net\framework64\v4.0.30319, but I'm not sure of the entire path on your machine. Then run the command aspnet_regiis -i.
Then try your web page again.
2) If you then get a 404.2 error, then open your IIS Manager, click on the machine name and then click on ISAPI and CGI restrictions. Make sure the .NET frameworks are set to Allow there.
By default, IIS6 does not serve .json (no wildcard MIME type).
Therefore a 404 not found is thrown. I then add a new MIME type (.json, text/plain or application/x-javascript or application/json) which works fine.
However, when you then add a new mapping (Home Directory -> Configuration -> Add) with .json, C:\WINDOWS\system32\inetsrv\asp.dll, "GET,POST" and try to browse to the file, you get a 404.
If you remove the mapping and try and POST or GET to it, you get a 405.
...
Suggestions?
By default, IIS in W2K3 and above won't serve files that aren't of a MIME type that it knows about (instead returning 404 errors).
You need to add a MIME type to IIS to allow it to serve that type of file. You can set it at the site level or at the server level.
To set this for the entire server:
Open the properties for the server in IIS Manager and click MIME Types
Click "New". Enter "JSON" for the extension and "application/json" for the MIME type.
Update
Given this post is found in the Sencha "getting started guide", I thought it's worth upgrading the steps.
On Win 7 Enterprise SP 1 with 64-bit
The IIS has a different outlook. So the steps:
*. Open IIS Manager. Then you get following window.
*. Right click on MIME and choose open feature
*. Click on ADD from top right corner Actions menu
*. Rest is as per Evan's.
Make sure you have Active Server Pages Allowed in the Web Service Extensions section of your IIS configuration.
IIS Manager -> (local computer) -> Web Service Extensions -> Active Server Pages
If you don't have IIS installed, obviously, you'll want to install it prior to launching the IIS Manager. I needed (on Windows 7) to go to: 'control panel/program and features' then click 'turn windows features on or off'
Reference: http://www.howtogeek.com/howto/windows-vista/how-to-install-iis-on-windows-vista/
It appears that starting the IIS Manager is different for different systems. I did 'start/run/inetmgr.
Reference: http://msdn.microsoft.com/en-us/library/bb763170(v=vs.100).aspx
Reference: http://technet.microsoft.com/en-us/library/cc770472(v=ws.10).aspx
Troy Frericks.
#