CookieDisabledException -------------7.1.8
The following CookieDisabledException is being occurred in logs ? when it occurs generally ?
I see multiple posts on PDN & mesh to resolve this exception ,but there are two different solutions for this .
https://pdn.pega.com/support-articles/pega-login-fails-cookiedisabledexception
>> prconfig/authentication/redirectguests/default value to false in 'Pega-Engine
>><env name="http/setsecurecookie" value="false" />
which setting should be modified to suppress this exception
The following CookieDisabledException is being occurred in logs ? when it occurs generally ?
I see multiple posts on PDN & mesh to resolve this exception ,but there are two different solutions for this .
https://pdn.pega.com/support-articles/pega-login-fails-cookiedisabledexception
>> prconfig/authentication/redirectguests/default value to false in 'Pega-Engine
>><env name="http/setsecurecookie" value="false" />
which setting should be modified to suppress this exception
com.pega.pegarules.priv.context.CookieDisabledException;com.pega.pegarules.priv.context.CookieDisabledException: An error has occurred which indicates that your browser does not support Cookies. You must enable Cookies in order to use this application; at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.establishRuntimeContext(HttpAPI.java:5222); at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.handleAuthentication(HttpAPI.java:2552); at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:548); at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:383); at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source); at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43); at java.lang.reflect.Method.invoke(Method.java:483); at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1270); at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008); at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:841); at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:331); at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:850); at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:315); at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263); at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:240); at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:278); at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:223); at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:574); at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:374); at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source); at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43); at java.lang.reflect.Method.invoke(Method.java:483); at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367); at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408); at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223); at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272); at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doPost(WebStandardBoot.java:121); at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doGet(WebStandardBoot.java:92); at javax.servlet.http.HttpServlet.service(HttpServlet.java:734); at javax.servlet.http.HttpServlet.service(HttpServlet.java:847); at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295); at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214); at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231); at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149); at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420); at org.jboss.as.web.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:134); at org.jboss.as.web.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:99); at org.jboss.as.web.session.JvmRouteValve.invoke(JvmRouteValve.java:92); at org.jboss.as.web.session.LockingValve.invoke(LockingValve.java:64); at org.jboss.web.rewrite.RewriteValve.invoke(RewriteValve.java:272); at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169); at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145); at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97); at org.jboss.web.rewrite.RewriteValve.invoke(RewriteValve.java:466); at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102); at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344); at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856); at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653); at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926); at java.lang.Thread.run(Thread.java:745);
Pegasystems Inc.
US
Hi Brahmeswara,
The root causes of the below two articles are different and based on your root cause you can try the corresponding solution.
Kindly go through the below PDN articles which will explain you the root cause of the two issues,
https://community.pega.com/support/support-articles/problem-sso-login-after-upgrade-pega-718
As your environment is v7.1.8, I feel the issue might be due to the first PDN article. Hope this might help you to judge the issue you are facing.
Regards,
Mahesh
Pegasystems Inc.
SG
The most common reason I found when I see this error is because the application had the "http/setsecurecookie" set to true and they were accessing the application through a non-secure URL (http instead of https).
The setsecurecookie setting controls the authentication cookie so that it would only be sent back to the client if the connection is secure. Without the authentication cookie, when the client sends a subsequent request to Pega, it will throw the exception CookieDisabledException.
Pegasystems Inc.
US
Hi Brahmeswara,
The issue is not specific to the upgrade, but it is related to the secure connection. If you had set the property "HTTP/SetSecureCookie" to true and you try to access the application in HTTP mode then you will notice this issue because the application expecting you to connect through HTTPS mode. So i feel it might be helpful to you if yours was the same scenario.
Regards,
Mahesh
Pegasystems Inc.
US
what is your use case? Are you using IAC (Pega Web Mashup)? authentication/redirectguests should only be set to false for IAC.
Skandiabanken
SE
Hi Kevin ,
Since it's coming in prod logs we couldn't identify the use case that involved around this.
The application is being accessed through secure URL only .
we are not using IAC .