Skip to content

oidc visibility mod #1377

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

Merged
merged 1 commit into from
Jul 17, 2025
Merged

oidc visibility mod #1377

merged 1 commit into from
Jul 17, 2025

Conversation

parmesant
Copy link
Contributor

@parmesant parmesant commented Jul 15, 2025

Fixes #XXXX.

Description


This PR has:

  • been tested to ensure log ingestion and log query works.
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added documentation for new or modified features or behaviors.

Summary by CodeRabbit

  • New Features
    • Made the OIDC module and its related authentication functions accessible for external use.

Copy link
Contributor

coderabbitai bot commented Jul 15, 2025

Walkthrough

The changes make several functions in the OIDC handler file public and expose the OIDC module itself via the library root. No internal logic or control flow is altered; only visibility is updated to allow external access to these functions and the module.

Changes

File(s) Change Summary
src/handlers/http/oidc.rs Changed six functions from private to public visibility.
src/lib.rs Changed oidc module from private to public visibility.

Suggested reviewers

  • nikhilsinhaparseable

Poem

In the warren of code, new doors now swing wide,
OIDC’s secrets no longer must hide.
Public and proud, functions hop into view,
Ready for callers—old friends and new!
With modules exposed, our journey’s begun,
Code rabbits rejoice, for sharing is fun! 🐇✨


📜 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 1fee5a7 and 9ef49ea.

📒 Files selected for processing (2)
  • src/handlers/http/oidc.rs (6 hunks)
  • src/lib.rs (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • src/lib.rs
  • src/handlers/http/oidc.rs
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: coverage
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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
Contributor

@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: 1

🔭 Outside diff range comments (6)
src/handlers/http/oidc.rs (6)

261-272: Add documentation for the newly public function.

Since this function is now part of the public API, it should have proper documentation explaining its purpose, parameters, and return value.

+/// Creates an HTTP redirect response to the specified URL with optional cookies.
+/// 
+/// # Arguments
+/// * `url` - The destination URL for the redirect
+/// * `cookies` - Iterator of cookies to include in the response
+/// 
+/// # Returns
+/// Returns an HTTP 301 (Moved Permanently) response with the redirect location and cookies
 pub fn redirect_to_client(
     url: &str,
     cookies: impl IntoIterator<Item = Cookie<'static>>,
 ) -> HttpResponse {

282-289: Add documentation for the newly public function.

Since this function is now part of the public API, it should have proper documentation explaining its purpose and usage.

+/// Creates a session cookie with the specified ULID.
+/// 
+/// # Arguments
+/// * `id` - The ULID to use as the session identifier
+/// 
+/// # Returns
+/// Returns a configured session cookie with appropriate security settings
 pub fn cookie_session(id: Ulid) -> Cookie<'static> {

291-298: Add documentation for the newly public function.

Since this function is now part of the public API, it should have proper documentation explaining its purpose and usage.

+/// Creates a username cookie with the specified username.
+/// 
+/// # Arguments
+/// * `username` - The username to store in the cookie
+/// 
+/// # Returns
+/// Returns a configured username cookie with appropriate security settings
 pub fn cookie_username(username: &str) -> Cookie<'static> {

319-340: Add documentation and consider consistency with existing user management APIs.

This function directly manipulates user metadata and cache. Since there's already a put_user function in the rbac module, ensure consistency between these APIs.

+/// Creates or updates a user in both metadata storage and local cache.
+/// 
+/// # Arguments
+/// * `username` - The username for the user
+/// * `group` - Set of roles/groups for the user
+/// * `user_info` - User information from OIDC provider
+/// 
+/// # Returns
+/// Returns the created/updated User or an ObjectStorageError
+/// 
+/// # Errors
+/// Returns ObjectStorageError if metadata operations fail
 pub async fn put_user(

342-373: Add documentation for the newly public function.

Since this function is now part of the public API, it should have proper documentation explaining its purpose, parameters, and behavior.

+/// Updates a user's roles and information if they have changed.
+/// 
+/// # Arguments
+/// * `user` - The existing user to potentially update
+/// * `group` - New set of roles/groups
+/// * `user_info` - New user information from OIDC provider
+/// 
+/// # Returns
+/// Returns the updated User (or unchanged if no updates needed) or an ObjectStorageError
+/// 
+/// # Errors
+/// Returns ObjectStorageError if metadata operations fail
 pub async fn update_user_if_changed(

300-315: Reduce visibility of internal OIDC token handler

This helper is only ever called within src/handlers/http/oidc.rs and doesn’t need to be part of the public API surface. Making it private prevents accidental external use of core token-handling logic.

• File: src/handlers/http/oidc.rs
Change the function signature from public to private:

- pub async fn request_token(
+ async fn request_token(
    oidc_client: Arc<DiscoveredClient>,
    login_query: &Login,
) -> anyhow::Result<(Claims, Userinfo)> {
    …
}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 651f067 and 1fee5a7.

📒 Files selected for processing (2)
  • src/handlers/http/oidc.rs (6 hunks)
  • src/lib.rs (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: de-sh
PR: parseablehq/parseable#0
File: :0-0
Timestamp: 2025-03-20T15:50:45.435Z
Learning: Pay close attention to code comments for typos and semantic clarity during reviews for the Parseable project.
🧬 Code Graph Analysis (1)
src/handlers/http/oidc.rs (2)
src/rbac/user.rs (1)
  • username (80-88)
src/rbac/mod.rs (1)
  • put_user (52-55)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
  • GitHub Check: coverage
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu

@nitisht nitisht merged commit f9a07ca into parseablehq:main Jul 17, 2025
13 checks passed
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