Sessions in the Dev Portal

    When a user logs in to the Dev Portal with their credentials, the Sessions Plugin will create a session cookie. The cookie is used for all subsequent requests and is valid to authenticate the user. The session has a limited duration and renews at a configurable interval, which helps prevent an attacker from obtaining and using a stale cookie after the session has ended.

    The Session configuration is secure by default, which may if using HTTP or different domains for portal_api_url and . Even if an attacker were to obtain a stale cookie, it would not benefit them since the cookie is encrypted. The encrypted session data may be stored either in Kong or the cookie itself.

    To enable sessions authentication, configure the following:

    • "secret":"<SET_SECRET>": The secret used in keyed HMAC generation. Although the Session Plugin’s default is a random string, the secret must be manually set for use with the Dev Portal since it must be the same across all Kong workers/nodes.
    • "storage":"kong": Where session data is stored. This value must be set to kong for use with the Dev Portal.
    • : The duration (in seconds) that the session will remain open; 3600 by default.
    • "cookie_renew":<NUMBER_OF_SECONDS_LEFT_TO_RENEW>: The duration (in seconds) of a session remaining at which point the Plugin renews the session; 600 by default.
    • "cookie_secure":<SET_DEPENDING_ON_PROTOCOL>: true by default. See for exceptions.
    • "cookie_samesite":"<SET_DEPENDING_ON_DOMAIN>": "Strict" by default. See Session Security for exceptions.
    • logout_methods
    • logout_query_arg
    • logout_post_arg

    For detailed descriptions of each configuration property, see the .

    The Session configuration is secure by default, so the cookie uses the , and SameSite directives.

    ⚠️Important: The following properties must be altered depending on the protocol and domains in use:

    • If using HTTP instead of HTTPS:
    • If using different subdomains for the and portal_gui_host, see the example below for .

    If using HTTPS and hosting Dev Portal API and the Dev Portal GUI from the same domain, the following configuration could be used for Basic Auth:

    In testing, if using HTTP, the following configuration could be used instead:

    Domains

    The dev portal portal_gui_host and the dev portal api portal_api_url must share a domain or subdomain. The following example assumes subdomains of portal.xyz.com and portalapi.xyz.com. Set a subdomain such as "cookie_domain": ".xyz.com" and set cookie_samesite to off.