Skip to content

RORDEV-1446-Add-support-for-the-passing-any-SAML/OIDC-config-parameters-via-kibana.yml #256

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

Conversation

Dzuming
Copy link
Collaborator

@Dzuming Dzuming commented Apr 11, 2025

Summary by CodeRabbit

  • Documentation
    • Enhanced the configuration guides with new sections for SAML authentication, enabling customization through additional parameters.
    • Improved the OIDC documentation with a dedicated section that explains how to fine-tune client and issuer settings, with examples for various setups.

@Dzuming Dzuming requested a review from Copilot April 11, 2025 05:44
Copy link

coderabbitai bot commented Apr 11, 2025

Walkthrough

The documentation in kibana.md has been updated to include new sections for configuring advanced authentication in ReadonlyREST Enterprise. It now provides additional guidance on customizing SAML and OIDC integrations by introducing "Additional Parameters" sections. These sections include parameter references with examples for handling specific integration needs, covering both SAML service provider and OIDC client configurations across different Kibana versions.

Changes

File Summary of Changes
kibana.md Added new Additional Parameters sections for SAML and OIDC authentication configurations, including example configurations and references to supported parameters.

Suggested reviewers

  • coutoPL

Poem

Oh, I'm a bunny with a joyful hop,
Nibbling on docs that never stop.
SAML and OIDC now gleam so bright,
Configs enriched by carrot-light.
Hopping through changes with eager cheer,
A rabbit’s delight—let’s give a cheer!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bbcb2eb and 4e8e8bf.

📒 Files selected for processing (1)
  • kibana.md (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • kibana.md

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (2)

kibana.md:1231

  • [nitpick] Consider aligning the YAML key structure with the SAML configuration block (which uses a top-level 'readonlyrest_kbn:' key followed by an indented 'auth:' block) to enhance consistency.
readonlyrest_kbn.auth:

kibana.md:1248

  • [nitpick] Consider aligning the YAML key structure with the SAML configuration block (which uses a top-level 'readonlyrest_kbn:' key followed by an indented 'auth:' block) to enhance consistency.
readonlyrest_kbn.auth:

kibana.md Outdated
When configuring SAML authentication in ReadonlyREST Enterprise, you can provide additional parameters to customize the behavior of the SAML service provider integration.
These parameters allow for fine-tuning the SAML integration to work with various identity providers and specific configurations

You can find a list of all supported parameters in a [documentation](https://github.com/node-saml/passport-saml/tree/3.x?tab=readme-ov-file#config-parameter-details)
Copy link
Preview

Copilot AI Apr 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] Consider updating the link text to be more descriptive (e.g., 'Passport-SAML Configuration Parameters') rather than a generic 'documentation' label.

Suggested change
You can find a list of all supported parameters in a [documentation](https://github.com/node-saml/passport-saml/tree/3.x?tab=readme-ov-file#config-parameter-details)
You can find a list of all supported parameters in the [Passport-SAML Configuration Parameters documentation](https://github.com/node-saml/passport-saml/tree/3.x?tab=readme-ov-file#config-parameter-details)

Copilot uses AI. Check for mistakes.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
kibana.md (2)

1064-1071: SAML Additional Parameters Documentation Update

The new "Additional Parameters" section for SAML is clear and informative. It appropriately explains that extra parameters can be passed to fine-tune the SAML service provider integration. Two specific suggestions:

  • Provide a YAML snippet example: For consistency with the OIDC section later on, consider adding a sample YAML code block that shows how users can pass these parameters via kibana.yml. This will help readers quickly see an example usage.
  • Fix a stray backtick: In the sample snippet (if present), the audience URL appears with a trailing backtick. For example, change:
    -              audience: "https://sp.example.com/metadata"`
    +              audience: "https://sp.example.com/metadata"

1219-1267: OIDC Additional Parameters Documentation Update

The added section on configuring additional parameters for OpenID Connect (OIDC) is comprehensive and well-structured. It provides both high-level guidance and concrete YAML examples (for issuer and client additional parameters) along with links to external documentation for further details. A couple of minor points for enhancement:

  • Verify that the indentation and formatting in the YAML examples are consistent with the rest of the documentation.
  • Double-check that all example values (e.g., URLs and placeholders) are clearly marked as examples so users know they need to be customized.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7a27871 and bbcb2eb.

📒 Files selected for processing (1)
  • kibana.md (2 hunks)

Copy link
Contributor

@sscarduzio sscarduzio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yay!

@Dzuming Dzuming merged commit 52a218c into develop Apr 12, 2025
3 checks passed
@coutoPL coutoPL deleted the RORDEV-1446-Add-support-for-the-passing-any-SAML/OIDC-config-parameters-via-kibana.yml branch April 24, 2025 18:12
coutoPL pushed a commit that referenced this pull request Apr 24, 2025
…rs-via-kibana.yml (#256)

* RORDEV-1446-Add-support-for-the-passing-any-SAML/OIDC-config-parameters-via-kibana.yml

* RORDEV-1446 review comment
Dzuming added a commit that referenced this pull request Apr 26, 2025
* commit new action strings

* [RORDEV-1317] ror-tools patching confirmation docs (#251)

Docs

* RORDEV-1262 improvements

* RORDEV-1262 improvements

* RORDEV-1262 Add documentation for extending Kibana API with x-ror-tenancy-id header (#253)

* RORDEV-1262 Add documentation for extending Kibana API with x-ror-tenancy-id header

* RORDEV-1262 Add info about id

* RORDEV-1262 add info about default value

* update description

* update based on coderabbit suggestions

* update message

* change endpoint to /tenants

* RORDEV-1444 user info source methods description (#252)

* RORDEV-1446-Add-support-for-the-passing-any-SAML/OIDC-config-parameters-via-kibana.yml (#256)

* RORDEV-1446-Add-support-for-the-passing-any-SAML/OIDC-config-parameters-via-kibana.yml

* RORDEV-1446 review comment

* commit new action strings

* commit new action strings

* commit new action strings

* commit new action strings

* RORDEV-1262 adjust endpoint

* RORDEV-1262 cr comments resolving

* RORDEV-1262 improvements

* RORDEV-1262 improvements

* update description

* update based on coderabbit suggestions

* update message

* change endpoint to /tenants

* RORDEV-1262 adjust endpoint

* RORDEV-1262 cr comments resolving

* RORDEV-1262 change example

* RORDEV-1262 change all tenants to user's tenants

* RORDEV-1262 change methods

---------

Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: mgoworko <37329559+mgoworko@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants