Skip to main content

Sun's Certificate supplied with Glassfish has expired !

27 replies [Last post]
suttridge_farm
Offline
Joined: 2006-01-27
Points: 0

Hi All,

Just to get in here straight away with a problem with Glassfish :-

[
Version: V1
Subject: OU=Secure Server Certification Authority, O="RSA Data Security, Inc.", C=US
Signature Algorithm: MD2withRSA, OID = 1.2.840.113549.1.1.2
Key: Sun RSA public key, 1000 bits
modulus: 6144706769222379850430183405655235862870193813433361902309516534729547168229223442088128897090426025874990958624426272027915771330043379079076269082776443120496525109458437435793974957144923190172655546279112796066635455545786300647745888353781002359412766112775410851780140804282673804950495744761467
public exponent: 65537
Validity: [From: Wed Nov 09 02:00:00 SAST 1994,
To: Fri Jan 08 01:59:59 SAST 2010]
Issuer: OU=Secure Server Certification Authority, O="RSA Data Security, Inc.", C=US
SerialNumber: [ 02ad667e 4e45fe5e 576f3c98 195eddc0]
]
Algorithm: [MD2withRSA]
Signature:
0000: 65 DD 7E E1 B2 EC B0 E2 3A E0 EC 71 46 9A 19 11 e.......:..qF...
0010: B8 D3 C7 A0 B4 03 40 26 02 3E 09 9C E1 12 B3 D1 ......@&.>......
0020: 5A F6 37 A5 B7 61 03 B6 5B 16 69 3B C6 44 08 0C Z.7..a..[.i;.D..
0030: 88 53 0C 6B 97 49 C7 3E 35 DC 6C B9 BB AA DF 5C .S.k.I.>5.l....\
0040: BB 3A 2F 93 60 B6 A9 4B 4D F2 20 F7 CD 5F 7F 64 .:/.`..KM. .._.d
0050: 7B 8E DC 00 5C D7 FA 77 CA 39 16 59 6F 0E EA D3 ....\..w.9.Yo...
0060: B5 83 7F 4D 4D 42 56 76 B4 C9 5F 04 F8 38 F8 EB ...MMBVv.._..8..
0070: D2 5F 75 5F CD 7B FC E5 8E 80 7C FC 50 ._u_........P
];_RequestID=8663f808-0948-4a87-8f79-19e0b3052142;|SEC5054: Certificate has expired: [
[
Version: V1
Subject: OU=Secure Server Certification Authority, O="RSA Data Security, Inc.", C=US
Signature Algorithm: MD2withRSA, OID = 1.2.840.113549.1.1.2
Key: Sun RSA public key, 1000 bits
modulus: 6144706769222379850430183405655235862870193813433361902309516534729547168229223442088128897090426025874990958624426272027915771330043379079076269082776443120496525109458437435793974957144923190172655546279112796066635455545786300647745888353781002359412766112775410851780140804282673804950495744761467
public exponent: 65537
Validity: [From: Wed Nov 09 02:00:00 SAST 1994,
To: Fri Jan 08 01:59:59 SAST 2010]
Issuer: OU=Secure Server Certification Authority, O="RSA Data Security, Inc.", C=US
SerialNumber: [ 02ad667e 4e45fe5e 576f3c98 195eddc0]
]
Algorithm: [MD2withRSA]
Signature:
0000: 65 DD 7E E1 B2 EC B0 E2 3A E0 EC 71 46 9A 19 11 e.......:..qF...
0010: B8 D3 C7 A0 B4 03 40 26 02 3E 09 9C E1 12 B3 D1 ......@&.>......
0020: 5A F6 37 A5 B7 61 03 B6 5B 16 69 3B C6 44 08 0C Z.7..a..[.i;.D..
0030: 88 53 0C 6B 97 49 C7 3E 35 DC 6C B9 BB AA DF 5C .S.k.I.>5.l....\
0040: BB 3A 2F 93 60 B6 A9 4B 4D F2 20 F7 CD 5F 7F 64 .:/.`..KM. .._.d
0050: 7B 8E DC 00 5C D7 FA 77 CA 39 16 59 6F 0E EA D3 ....\..w.9.Yo...
0060: B5 83 7F 4D 4D 42 56 76 B4 C9 5F 04 F8 38 F8 EB ...MMBVv.._..8..
0070: D2 5F 75 5F CD 7B FC E5 8E 80 7C FC 50 ._u_........P
]

Regards,

Steve.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Necris
Offline
Joined: 2013-08-16
Points: 0

Hi everyone,

I had been sufering also this problem in serveral servers and some of it's complications, that I have been able to resolve after quite a bit of investigation.

1st make a backup of the involved files... because maybe this is not exacly your case and you will want to begin at the starting point.

Error 1: Certificate expired

Solution 1: This one is the easyone to resolve:

Basicaly enter de config dir, remove the key from the CA file and restart grassfish.
cd /domain//conf
keytool -delete -alias gtecybertrust5ca -keystore cacerts.jks -storepass myMasterPwd
Default master passowrd is "changeit".

Error 2: IIOP lazy-init...

Solution:
Unfortunately i respondend to simptoms here and dissabled the lazy-init... but didn't notice that i was cause because the system injected here SSL configuration for the IIOP binded in the 3700 port... (not compatible with lazy-init) without a set alias ""....

So remove this line

Leaving the listener like it was before

After both modifications restart glassfish.

What can I say... a CA expires and generates these kind of problems?? quite strange... and time consuming...

Hope this saves tames to someone else ;)

edrandall
Offline
Joined: 2006-03-01
Points: 0

Even with more recent Glassfish 2 downloads containing JDK1.6.0_18 and 1.6.0_20, this problem still persists, because the expired certificate has not been removed from the template stores.

A copy of the expired certificate also lives in (and should be deleted from) these keystores:

{installdir}/lib/install/templates/cacerts.jks
{installdir}lib/install/templates/ee/cacerts.jks

keytool -delete -v -alias verisignserverca -keystore lib/install/templates/cacerts.jks
keytool -delete -v -alias verisignserverca -keystore lib/install/templates/ee/cacerts.jks

The default master password required is "changeit".

whyemail
Offline
Joined: 2010-02-20
Points: 0

Hi all
I tried run the following command to delete the certification.
asadmin stop-domain --domaindir=/cluster/home/mmas/nodes/DAS/domains domain1
/opt/jdk1.6.0_16/bin/keytool -delete -v -alias verisignserverca -keystore /cluster/home/mmas/nodes/DAS/domains/domain1/config/cacerts.jks
asadmin start-domain --domaindir=/cluster/home/mmas/nodes/DAS/domains domain1
 
The old error missed, but it create a new one.
[#|2010-02-20T11:37:27.002+0800|WARNING|sun-glassfish-comms-server2.0|javax.ee.enterprise.system.tools.admin|_ThreadID=24;_ThreadName=httpWorkerThread-5003-0;_RequestID=030fa3cd-426b-4b0c-a24c-488383dc2562;|EEADM0002: An exception occurred starting the server instance traffic_instance_PL-2-3.
com.sun.enterprise.ee.admin.servermgmt.AgentException: Error unmarshaling return header; nested exception is:
        java.io.EOFException
        at com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.mangleInvokeException(NodeAgentProxy.java:301)
        at com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.invoke(NodeAgentProxy.java:345)
        at $Proxy43.startInstance(Unknown Source)
        at com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.startServerInstance(ServersConfigBean.java:377)
        at com.sun.enterprise.ee.admin.mbeans.ServersConfigMBean.startServerInstance(ServersConfigMBean.java:173)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
        at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
        at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
        at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
        at $Proxy1.invoke(Unknown Source)
        at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
        at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)
        at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
        at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
        at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
        at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
        at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
        at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:117)
Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
        java.io.EOFException
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:209)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
        at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
        at com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.invoke(NodeAgentProxy.java:338)
        ... 52 more
Caused by: java.io.EOFException
        at java.io.DataInputStream.readByte(DataInputStream.java:250)
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:195)
        ... 57 more
|#]
[#|2010-02-20T11:43:32.095+0800|SEVERE|sun-glassfish-comms-server2.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.admin.server.core.AdminServiceLifeCycle@413803ba;com.sun.appserv.server.ServerLifecycleException: java.lang.RuntimeException: Unable to save stub to /cluster/home/mmas/nodes/DAS/domains/domain1/config/admch;|Service com.sun.enterprise.admin.server.core.AdminServiceLifeCycle@413803ba cannot be initialized! : com.sun.appserv.server.ServerLifecycleException: java.lang.RuntimeException: Unable to save stub to /cluster/home/mmas/nodes/DAS/domains/domain1/config/admch|#]

Shell we add a new key for it?

mayfri13
Offline
Joined: 2010-02-01
Points: 0

Help me

josealvarezdelara
Offline
Joined: 2008-12-26
Points: 0

Thanks a lot all of you.

I think the problem was GF was to deep from the root of the path.
I have instealled it in the root C:\ and I have resolved the issue.

Best Regards,
Jose

josealvarezdelara
Offline
Joined: 2008-12-26
Points: 0

Hello,

I did one by one every step you say. My OS is WinXP.

And now when I start GF V3 from NB 6.8 it works ok,
but when I try from then command line I get the following,

FATAL ERROR in native method: processing of -javaagent failed
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
4)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(Instrument
ationImpl.java:133)
Exception in thread "main"

If I can leave it as it is I do it, but I want to be sure I will not have problems. I say from inside NB 6.8 it works ok and that is what I need.

Best Regards,
Jose

Dies Koper

Hi Jose,

Are you sure you specified the path of the right JDK at step 1)?
It looks like the PATH now includes a different (older) JDK than what
you had previously. Please try starting GF again after changing the PATH
setting to whatever it was when you could successfully run GF last
(which probably included a path to JDK 6).

Regards,
Dies

On 19/01/2010 10:45, glassfish@javadesktop.org wrote:
> Hello,
>
> I did one by one every step you say. My OS is WinXP.
>
> And now when I start GF V3 from NB 6.8 it works ok,
> but when I try from then command line I get the following,
>
> FATAL ERROR in native method: processing of -javaagent failed
> java.lang.UnsupportedClassVersionError: Bad version number in .class file
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
> 4)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(Instrument
> ationImpl.java:133)
> Exception in thread "main"
>
> If I can leave it as it is I do it, but I want to be sure I will not have problems. I say from inside NB 6.8 it works ok and that is what I need.
>
> Best Regards,
> Jose
> [Message sent by forum member 'josealvarezdelara' (dakhla.0563@hotmail.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=381593
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

josealvarezdelara
Offline
Joined: 2008-12-26
Points: 0

Hi,

I have installed update 18 of Java SE 6 and later NB 6.8 with GF v3
and the same history: Certificate has expired

Please, how to fix it?

Thanks in advance,
Jose

edrandall
Offline
Joined: 2006-03-01
Points: 0

The certificate seems to be copied into the domain config from the JDK when the
Glassfish domain is created, so eventually will need to remove it from both the
domain and from the JDK to ensure that this error will not return.

Also, you cannot perform operations on the keystore unless you have a
"master password" set up.
We had it set to an empty string, which keytool will not accept.

Here is what I just had to do to fix this in our Glassfish v2.1 development domains:

1) Set your PATH for the appropriate JDK
$ PATH=/opt/glassfish/jdk/bin:/opt/glassfish/bin:$PATH

2) Stop Glassfish
$ asadmin stop-domain --domaindir=/path/to/domainparentdir domainName

3) Set a master password for the domain keystore
$ asadmin change-master-password --savemasterpassword=true --domaindir=/path/to/domainparentdir

4) Delete the offending certificate
$ keytool -delete -v -alias verisignserverca -keystore /path/to/domaindir/config/cacerts.jks
Enter keystore password:

5) Start the glassfish domain as usual
$ asadmin start-domain --domaindir=/path/to/domainparentdir domainName

monzillo
Offline
Joined: 2004-05-08
Points: 0

please see the following

http://blogs.sun.com/monzillo/entry/sec5054_certificate_has_expired

The Glassfish distribution contains a template truststore that was created from that of the JDK.
When a domain is created, the template is used to create the truststore of the domain. You can correct an existing domain by removing the expired cert from its truststore, and you can correct the template to prevent the certificate from being reintroduced in future domains.

tecknobabble
Offline
Joined: 2005-06-10
Points: 0

certutil -D -d "path-to-DAS domain-config-dir" -n verisignserverca

tecknobabble
Offline
Joined: 2005-06-10
Points: 0

Apologies for the typo, the certutil commands should have read:

certutil -D -d
-n verisignserverca

tecknobabble
Offline
Joined: 2005-06-10
Points: 0

If you are using an enterprise domain, which is the principle way you'd end up using NSS, then the certutil equivalent of the keytool command would be:

certutil -D -d
-n verisignserverca

you should be prompted for the domain's master password.

You should, of course, shutdown the domain, and take a backup of the cert8.db/key3.db/secmod.db files prior to doing this.

Shutting down any node agents and restarting them with --syncinstances=true (for 9.1/2.x) should result in the changed files being sync'd to all the other instances in the domain.

The message is just a warning, and shouldn't impact the function of the domain - the domain's own certificate is self-signed and doesn't rely on the verisign certificate at all.

sbeard
Offline
Joined: 2007-10-23
Points: 0

We are not using the Java cert store but am using the keystore database that comes bundled with the SUN build and accessed using certutil.

lightguard
Offline
Joined: 2007-09-26
Points: 0

The cert is from verisign (I believe) you wouldn't be able to generate a new cert. Best to either delete it or wait for the JDK upgrade that "should" fix it.

ealejandro101
Offline
Joined: 2004-05-04
Points: 0

Ok,

for now

the file to contain information about certificate is

... glassfish\domains\domain1\config\cacerts.jks

and, the problem is The date has expired into alias verisignserverca

Command used
keytool -list -v -alias [b]verisignserverca [/b] -keystore cacerts.jks

I not know the correct choise or solution... I will continue working

ealejandro101
Offline
Joined: 2004-05-04
Points: 0

Hi,

Reading a little on the subject, I think the solution is to generate a new certificate using the key tool.

The Sun GlassFish Enterprise Server v3 Administration Guide Book (available in web),
A theme of the book is about this subject

I hope have the solution today.

best regards

monzillo
Offline
Joined: 2004-05-08
Points: 0

just to be clear, "Sun's certificate" did not expire. The expired certificate
is a root certicicate that was used (apparently by RSA and pehaps later by Verisign)
starting back in 1994 to issue user certificates, all of which have also since expired.

riktam
Offline
Joined: 2006-05-09
Points: 0

Thanks for this info ! - with it i could find the solution:

In the config/domain.xml, you must change the line
"-Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}/config/cacerts.jks
"
to "-Djavax.net.ssl.trustStore=${com.sun.aas.javaRoot}/lib/security/cacerts"

On the next start, GlassFish looks for the default cacerts in JRE6-20 - and all works fine.

sorry, forgot this change

Message was edited by: riktam

monzillo
Offline
Joined: 2004-05-08
Points: 0

please see
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6852796

The expired root will be removed in update 18 of Java SE 6, (do out in about 5 days)
and we will also remove the cert from the Glassfish truststore.

You can also use keytool -delete to remove the cert (alias = verisignserverca) from your glassfish truststore. but you do not need to take any action, as all certs issued under the expired authority
will have also expired.

spennine
Offline
Joined: 2008-09-29
Points: 0

can someone from Sun offer some guidance here?

sbeard
Offline
Joined: 2007-10-23
Points: 0

We are also getting this accross many of our domains. Started happening yesterday.

qtxdaer
Offline
Joined: 2007-09-28
Points: 0

I have the same problem on all GlassFish domains I handle! How do we solve this?

shukla_aviral
Offline
Joined: 2010-01-08
Points: 0

Hi,

It is not working for me also.

Please provide a solution.

Thanks

justinwyer
Offline
Joined: 2008-11-24
Points: 0

I am experiencing this problem as well.

Kumar Jayanti

glassfish@javadesktop.org wrote:
> I am experiencing this problem as well.
> [Message sent by forum member 'justinwyer' (justin@lifeasageek.com)]
>
Thanks for reporting, we are looking into a solution. Will get back soon.

regards,
kumar

> http://forums.java.net/jive/thread.jspa?messageID=379545
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

bjornd
Offline
Joined: 2009-01-29
Points: 0

This is a show-stopper for me.
Does anyone have a workaround?