add Authorized redirect URIs explaination

[lirlia]

Summary by CodeRabbit

• Documentation
  • Updated the deployment manual with the latest instructions and guidelines.

[coderabbitai]

Walkthrough

The update to the deploy-manual.md file does not involve any code changes. It appears to be a general content update to a markdown document, which is part of the deployment manual. The specifics of the content change are not provided, hence the summary is limited to acknowledging a non-code related revision.

Changes

File Path	Change Summary
.../deploy-manual.md	Updated content in deployment manual; no code changes.

🐇✨📜
To the docs, a hop and a tweak,
A change so subtle, a peek not a leap.
Words woven with care, the manual refined,
By paws of a rabbit, with humans in mind. 🌟📖

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 783afbc and cc60edc.

Files selected for processing (1)

• docs/deploy-manual.md (1 hunks)

Additional comments: 2

docs/deploy-manual.md (2)

• 252-261: > Note: This review was outside the patches, and no patch overlapping with it was found. Original lines [10-10]

The addition of "Authorized redirect URIs" to the Table of Contents is a good way to inform the reader that there is now information available on this topic.

• 252-261: > Note: This review was outside the patches, so it was mapped to the patch with the greatest overlap. Original lines [1-258]

Overall, the documentation is well-structured and the new section on "Authorized redirect URIs" integrates seamlessly with the existing content. The formatting is consistent throughout the document, and the instructions are clear, which should help users in setting up their deployment correctly.

[coderabbitai]

The explanation of setting Authorized redirect URIs for the Identity-Aware Proxy Pattern is clear and concise. It's good that an example URI is provided, but it may be beneficial to explain why this specific URI format is required and what each part of the URI signifies.

- like: `https://iap.googleapis.com/v1/oauth/clientIds/[YOUR_CLIENT_ID]:handleRedirect`
+ like: `https://iap.googleapis.com/v1/oauth/clientIds/[YOUR_CLIENT_ID]:handleRedirect` (Here, `[YOUR_CLIENT_ID]` should be replaced with the actual client ID obtained from your OAuth credentials. This URI format is required by the Identity-Aware Proxy to correctly handle the OAuth redirect.)

---

Committable suggestion

❗ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	In this pattern, you need to set Authorized redirect URIs in OAuth credentials.
	like: `https://iap.googleapis.com/v1/oauth/clientIds/[YOUR_CLIENT_ID]:handleRedirect`
	In this pattern, you need to set Authorized redirect URIs in OAuth credentials.
	like: `https://iap.googleapis.com/v1/oauth/clientIds/[YOUR_CLIENT_ID]:handleRedirect` (Here, `[YOUR_CLIENT_ID]` should be replaced with the actual client ID obtained from your OAuth credentials. This URI format is required by the Identity-Aware Proxy to correctly handle the OAuth redirect.)