feat(app): dynamic authentication provider support #2167
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This change adds support for loading authentication providers or modules
from dynamic plugins. An environment variable
ENABLE_AUTH_PROVIDER_MODULE_OVERRIDE controls whether or not the backend
installs the default authentication provider module. When this override
is enabled dynamic plugins can be used to supply custom authentication
providers. This change also adds a "components" configuration for
frontend dynamic plugins, which can be used to supply overrides for the
AppComponents option. This is required for dynamic plugins to be able to
provide a custom SignInPage component, for example:
```
frontend:
my-plugin-package:
components:
- name: SignInPage
module: PluginRoot
importName: SignInPage
```
Where the named export SignInPage will be mapped to
`components.SignInPage` when the frontend is initialized.
Signed-off-by: Stan Lewis <[email protected]>
|
The image is available at: |
|
@gashcrumb: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
This change adds support for loading authentication providers or modules from dynamic plugins. An environment variable
ENABLE_AUTH_PROVIDER_MODULE_OVERRIDE controls whether or not the backend installs the default authentication provider module. When this override is enabled dynamic plugins can be used to supply custom authentication providers. This change also adds a "components" configuration for frontend dynamic plugins, which can be used to supply overrides for the AppComponents option. This is required for dynamic plugins to be able to provide a custom SignInPage component, for example:
Where the named export SignInPage will be mapped to
components.SignInPagewhen the frontend is initialized.PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer
I have an example using this plugin that just needs a bit more tidying up, once that's done I'll update this with a link and some steps to try this end to end.