You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2018/04/30 15:04:00 UTC

[jira] [Updated] (KNOX-1126) Templating of Params in Generated Topologies

     [ https://issues.apache.org/jira/browse/KNOX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Larry McCay updated KNOX-1126:
------------------------------
    Fix Version/s:     (was: 0.15.0)
                   Future

> Templating of Params in Generated Topologies
> --------------------------------------------
>
>                 Key: KNOX-1126
>                 URL: https://issues.apache.org/jira/browse/KNOX-1126
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>            Priority: Major
>             Fix For: Future
>
>
> Param templating in shared provider config and possibly of service params will be useful in order to limit the proliferation of provider config files and descriptors due to params that are specific to the deployment environment.
> For instance, SSOCookieProvider can be configured to use a particular public key for verifying the token signature. The public key is configured as a param with the PEM encoding minus the header and footer from the PEM file.
> The ability to template this as a macro or placeholder in the provider config will allow for the ability to leverage the same provider config for multiple deployment environments where the value will be extracted from the gateway config or runtime environment (like for the public key from the signing keystore).
> This will enable multiple clusters to discover the same provider config and descriptors from a single registry but still have deployment environment specific values.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)