Enterprise Client Community

Hi,

I think the basic problem is that we do not set the tooltip and we see the hotkey in that case.
And in this case the hotkey is not translated properly (Strg-X) in english where it should be Ctrl-X.

Can you check if there is some language issue here?

Tobias

Great! Thanks

Hello Captain,

can we have a switch in the PDFPrinter component that lets the print job fail in case the printer cannot be found on client side?

Background is some long discussion with a customer that wants to be sure that the printing is only done on a certain local printer. We already discussed the local printer issue in another forum topic, but we could convince the customer to agree on a solution where we pass the name of the printer to the client and fail the print job if the printer is not available on the client.

Tobias

Hello Michael,

I knew that we have the experts around that in the community!

So if I understand correctly you save the printer name for each user in the user record and pass it to your print control. That could be an option, but then we have to do the administration for each user.

I will try the hint with the Win32PrintService, but then we are platform-dependent, which is ok for this one customer, but not a general product solution.

Thanks a lot for you help!

Tobias

Hello Community,

we have the following requirement from a customer:
The user should only be able to print on printers that are locally attached to the clients machine. The reason behind this is that the information that should be printed is very sensitive (PIN letter).

I know that we have the pdfprinter component where we can restrict the printing to the standard printer. But this is not an option for the customer since the end user can change the standard printer.

After a bit of googling i could not find a way to find out any information about if the printer is connected locally or through the network.

Does anyone of the community have any experience with that? Is there some hint you can give me? Can we have it as a feature in the pdfprinter ;-)?

Tobias

Is there a way to remember the settings on client side, like having a cookie or a similar approach?
Currently we do not have "user preferences" on server side.

Tobias

Hello everyone,

when starting a CaptainCasa application as applet and then enable full screen mode you cannot switch back to non-full-screen using the standard Key F11. We had a customer having issues with that.

My explanation was that the Captain Casa is a RIA-Framework that intercepts all keystrokes in order to be able to react on keys application specific. Is that correct? Is there any workaround for that, so that some keys are not intercepted?

Tobias

I think you are right because Captain Casa has to fulfill the requirements for RIAs only and the two attributes are not necessary for this.

We had to add them in some components since we needed to access the Java components integrated in an applet which was called by javascript (live connect) and this call was blocked on high security level if these attributes were missing.

So for Captain Casa, you are on the safe side (for now, until Oracle comes up with the next surprise...)

Tobias

Hi Björn,

just to make sure we are on the same page: I just downloaded the latest version (5_0_20140120) and checked the Manifest. It seems that the two options that are necessary from 1.7_u51 onwards are missing:


<attribute name="Application-Library-Allowable-Codebase" value="*"/>
<attribute name="Caller-Allowable-Codebase" value="*"/>

Can you double-check?

Tobias

Hello community,

we faced the problem that our application was not running any more due to security constraints introduces with the latest Java update 1.7_u51 (14.01.2014).

Oracle raised the security level so that our application was not running properly any more.
To solve the problem, we had to do two things I want to share with you, in case you run into the same problems:

(1) We had to include the whole certificate chain into the PFX/PKCS12 container we used for signing. In our case we just signed the code with our signing certificate. But for running the application on client side, an intermediate certificate was missing so that the new Java version considered the jar file to be self-signed. I can provide details if you face the same problem.

(2) We had to include some security-related options to the MANIFEST.MF file. This is a snippet from the ANT script we use to generate the manifest file:
<manifest file="${build.dir}/MANIFEST.MF">
<attribute name="SVN-Revision" value="${svn.lastchanged.revision}" />
<attribute name="Specification-Vendor" value="Nexus Technology GmbH" />
<attribute name="Implementation-Vendor" value="Nexus Technology GmbH" />
<attribute name="Implementation-Version" value="${ivy.revision}" />
<attribute name="Permissions" value="all-permissions"/>
<attribute name="Codebase" value="*"/>

<attribute name="Application-Library-Allowable-Codebase" value="*"/>
<attribute name="Caller-Allowable-Codebase" value="*"/>
</manifest>

Hope this helps you avoid the problems.

Tobias

Thanks for the direct link to the changes.

Tobias

Hello Captain,

can you provided a link to the list of changes as part of every message that you post about new versions?
I always have to go to captaincasa.com and navigate to download->list of changes.
I know we should all have the captain casa page a start page in the browser, but the company policy wants us to see our intranet page there

Tobias

Well, then I guess you will have to wait for the next update I guess...

The documentation comes form Java 7, so I assume that you call jarsigner with Java 7.

Found the section it the documentation about the digestalg:

-digestalg algorithm
Specifies the name of the message digest algorithm to use when digesting the entries of a jar file.
See Appendix A of the Java Cryptography Architecture for a list of standard message digest algorithm names. If this option is not specified, SHA256 will be used. There must either be a statically installed provider supplying an implementation of the specified algorithm or the user must specify one with the -providerClass option, otherwise the command will not succeed.

This can be passed to your call of jarsigner. Try this

jarsigner -verify -verbose -digestalg SHA1 jpedal.jar