Child pages
  • Security Configurations

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


/usr/local/omk/bin/opcommon-cli.exe act=secrets_randomise [force=true] [length=N]


    • force=true will change the token even if this is not the default (Like =~ change_me)
    • length=N will force the token length to N (32 by default)


(tick) By defaultThe cookies are not going to be accesible from the JavaScript API.
(tick) Should be enabled by setting the configuration item "auth_secure_cookie" => "true" in opCommon.json.

This cookie could be sent just in a request ciphered over https protocol. That's the reason why it is not set by default. 


set to Strict

(warning) Will be supported in next versions. (Major version upgrade from libraries is required) 

The cookie set to strict means that the browser just send the cookie if the request was made in the website that originally stablished the cookie. 

Security Content Policy

The Security Content Policy is a http header that restricts how resources (Javascript, CSS, Images, etc.) are loaded from allowed sites. It will help to mitigate some attacks of Criss Site Scripting (XSS) and data injection. 

The default values can be overwritten setting the configuration item security_content_policy in the configuration file, opCommon.json.