Since today we have a permission problem when a new user starts our smartclient bootstrapper
See picture below, it says that we have to meet the security levels “high” or “very high”, implying that we do not meet them currently.
What we did so far without success is:
a) Sign the jnlp with our current certificate, which we used already for all plugins without any problems
b) Put the web location to the java exception list
Is there anything else we could do, except of not using the bootstrapper and turn to the traditional webstart method?
it would be very weird if traditional does work
Then there is something different between the signing… Because why would that work? Its just another jar that is started up
And with the traditional startup you really have to sign everything correctly, and with the bootstrapper you really only have to make sure that the bootstrapper is signed correctly
What does “Mehr Information” tell you? Does it tell a bit more what really is the problem? (then only that problem in “Ursache” that still doesn’t really tell us what is wrong
Are you sure the boostrap.jar is signed correctly? and does verify?
Yes, signing is correct with a valid certificate.
It looks like I should have reading the screen on “More Information” better.
Because that shows a screen that a tool called FortiGuard from FORTINET shows, telling it blocked the call and one should call support when thinking the block is not ok.
So my current assumption is that a new rule of that security software does not like the call of the bootstrapper due to some reason.
I already created a ticket for the responsible support team.
i wonder why, that is a very small applicaiton that does nothing more then some download of other stuff and start it up
I can’t make it much simpler then that…
that is the name of the class that you start
it is a bit tricky how to change that
i think if you start the bootstrapper with: java -Xdock:NiceName -jar bootstrap.jar it could work.
There is a comment which says, that it is not possible to set title of a dock icon:
Apple doesn’t provide any way to change title for dock icon for not bundled app, it is taking the process name instead, ‘java’ in our case.
For bundled apps this title can be changed by renaming app.
However -Xdock:name is still able to change title in menubar.
You ask for anybody else with this issue: I’m also looking for a way to change the app name from StandAloneBootstrap to our app name. And hoped for an argument, which can be defined in the properties file e. g. Thanks to your reply, I now know «java -Xdock:name=“My Application” -jar bootstrap.jar».
But what should I tell our users? How should they launch the application?
By the way: Is it only a Mac issue?
The problem of the dock icon and name, I did not notice so far.
I had the illusion, the switch to bootstrap would be easy.
We are launching our smart client apps with this new bootstrapper, without using jnlp and webstart.
How can I define e. g. the window title (servoy.branding.windowtitle)? Before (jnlp, webstart), this was defined in a profile on the Servoy admin page. Now, I edited the bootstrap.jar file and added
arg0=servoy.branding.windowtitle=ourAppName
to the properties file. But this had no effect.
Does anybody know, how this can be achieved? That would be appreciated a lot!
the branding stuff should work the same
They are still get just through properties not through a jnlp configuration
so if you have on the server: servoy.branding=true and then servoy.branding.windowtitle=appname
I tried so many different combinations, equal signs, colon, quotation marks, starting with arg1, deleting the setting on the server… Nothing works, everything is ignored. Do you have any suggestion? Did you try it yourself? Could anybody else make it work?
We use:
Servoy version 2020.3.1 -releaseNumber 3563
java.version=1.8.0_221
os.name=Mac OS X
os.version=10.14.6
Thanks, regards and best wishes for Christmas time
I think Johann means you can only set the branding on the server, not the client
[attachment=0]Bildschirmfoto 2021-01-11 um 14.15.38.png[/attachment]
This would be ok if you have one app on one server.
On the other hand because of the whole java-situation we switched to deploying executables/.app for our smartclients, and we can set the options in packr (Mac) / run4j (Windows).
Thank you for your response. This explains the observed behaviour: Setting the branding on the client is not possible.
We also switched to .app on macOS. Windows still open.
of the branding stuff, the servoy.branding.webstart.xxxx don’t work no (because there is no webstart)
but the others like servoy.branding.windowicon should just work. we do read those and set those on the Window/Frame object.
Those should just work.
