What is the relation bwetween glide.ui.secure_cookie sytem property and the secure flag set for an HTTP cookie?SummaryReferencing the 'Secure session cookies' documentation:https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/security/reference/secure-session-cookies.htmlThis "Secure session cookies" documentation says:When you set the property to true, authentication cookies contain only a token, and have no embedded user information.o On the service side, it looks up the token in the database, and associates it with a specific user. An authentication cookie can be used a single time only.o Once used, the cookie is invalidated and removed from the database so that it can't be used again. The service then issues a new cookie.So despite the name, there is no connection between the glide.ui.secure_cookie system property and the secure flag set for an HTTP cookie for an HTTPS session. The glide.ui.secure_cookie property was intended to restrict re-use of authentication cookies. However this seems to be the case whether the property is set to true (the default) or false. I believe the functionality of this legacy code was changed at some point and the documentation was not properly updated to reflect this.Self-hosted customers can implement the secure flag in their own infrastructure as ServiceNow does not implement it within an application. The secure flag for HTTP cookies (including JSESSION_ID) is configured to be set over HTTPS sessions by the webserver (e.g. Tomcat). "Despite the name, there is no connection between the glide.ui.secure_cookie system property and the secure flag set for an HTTP cookie for an HTTPS session."