My needs are the same as two years ago.
It is just that the market evolved and the SSL VPN appliance does not keep with the market as expected by me.
I have bolded the relevant part of your statement - your needs do not describe all of our customers' needs.
Since Java soon will not be supported by the main web browsers then the SSL VPN cannot be used either.
Without Java the SSL VPN tunnels cannot be established so why do you insist the product can be used?
SSL Tunnels are not the only feature of the product, nor are they the main feature. The SSL VPN's primary feature is Web Forwards, which can be used without the SSL VPN Agent in almost all cases. As I said, your needs are not the same as all customers needs. Many customers only need Web Forwards and are therefore perfectly happy with Java-less functionality. And for those that do need the agent, there is the Standalone Agent (link in the first post) which meets all of the Agent needs without having the Java browser plugin available.
If I would like to use a feature like certificate autentification in Edge it does not work because of Java. It used to work when I purchased the appliance. The screen freezes and I can not even return to insert the name of another user.
You should open a Support case about this - client certificate authentication does not require Java, it only requires support for client certificates in the browser, which Edge does have. Edge has never had support for Java applets, so if you say this used to work then you have proven that this feature is not Java-based and that you have a different issue here.
Also none of the SSL VPN Applications works. At least non of the ones I have. Are you able to use any of them?
The SSL Tunnels does not work either.
This is correct, this feature requires the Agent, which is available as a standalone app. This app continues working without Java support in the browser.
Network connector does not work without java.
IPsec server does not work without java.
These two are not correct, both of these features can be used without Java. Network Connector has a standalone client, IPsec simply configures the client which is built into Windows/OSX, therefore these clients can be configured by any other means and still work fine with the SSL VPN.
Do you believe that we can see the SSL VPN as a functional product in such circumstances?
Do you agree with a general understanding that if you receive some money for a product you should provide a product that works?
I do agree, and our product still works. There may be some minor changes caused by events outside of Barracuda's control (i.e. you will likely have to replace the applet-launched Agent with the standalone Agent, which has an identical workflow once running) but the product is just as functional today as it ever was.
I think by now we've probably had all the useful discussion that can come out of this - at this point, if you are unhappy with the continued functionality of your SSL VPN appliance then I would suggest speaking to our Sales team and discussing a migration to a NextGen Firewall (obviously we could provide you with a trial VM for you to verify the functionality first before purchase). They may be able to do something with the price based on your SSL VPN subscription status, but that is entirely up to the Sales team and I can't promise any discount.