This bug report is related to Smartclient v9.0p_2013-10-23.
You might get into trouble, if you might move the existing example "secureApp" into a tomcat-container. The login-path variable must be:
- without webapp-name -> otherwise the redirect from an unauthorized page does not work
- with webapp-name -> otherwise the cookie is bounded to the wrong URL and cannot be accessed from the actual login-page.
Solution:
Include the context path within the cookie-settings in com.isomorphic.servlet.ServletTools.java.
public static Cookie setCookie(RequestContext context, String name, String value, String path, String domain, int maxAge)
....
- cookie.setPath(path)
+ cookie.setPath(context.getContextPath() + path);
You might get into trouble, if you might move the existing example "secureApp" into a tomcat-container. The login-path variable must be:
- without webapp-name -> otherwise the redirect from an unauthorized page does not work
- with webapp-name -> otherwise the cookie is bounded to the wrong URL and cannot be accessed from the actual login-page.
Solution:
Include the context path within the cookie-settings in com.isomorphic.servlet.ServletTools.java.
public static Cookie setCookie(RequestContext context, String name, String value, String path, String domain, int maxAge)
....
- cookie.setPath(path)
+ cookie.setPath(context.getContextPath() + path);