-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RHIDP-5489 Enabling authentication with your authentication provider #891
base: main
Are you sure you want to change the base?
Conversation
Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-891/ @ 02/04/25 13:23:46 |
. link:{installing-and-viewing-dynamic-plugins-url}#assembly-third-party-plugins[Export, package, and install your custom plugins]. | ||
. Add your custom plugins configuration to `dynamic-plugins.yaml` in {product-short}. | ||
+ | ||
.`dynamic-plugins.yaml` excerpt for LDAP catalog support |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gashcrumb Does the dynamic-plugins.yaml
file content need to be that long? I would assume that if the plugins has defined default values, it is sufficient to enable the plugin. Is it correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe these LDAP plugins aren't a great example, most of the config here is concerned with getting these plugins to talk to LDAP. It's probably less important than the touch points where the user is required to integrate either configuration or code to connect authentication providers to the RHDH app. I have just finished up another example that I could walk you through if you like here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At first sight this example is maybe even more complex, because we have 4 plugins.
Would an example plugin defining static users be sufficient for the demonstration purpose? Or is it a requirement to delegate authentication to an external service?
…ovider Signed-off-by: Fabrice Flore-Thébault <[email protected]>
...es/authentication/proc-enabling-authentication-with-your-custom-authentication-provider.adoc
Show resolved
Hide resolved
…custom-authentication-provider.adoc
Enabling authentication with your custom authentication provider.
Preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-891/authentication/#enabling-authentication-with-your-custom-authentication-provider
IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.5
Add the relevant labels to the Pull Request.
Issue: https://issues.redhat.com/browse/RHIDP-5489