Skip to content

feat: add a reason field before PAM account access#189

Open
carlosmonastyrski wants to merge 4 commits intomainfrom
feature/PAM-184
Open

feat: add a reason field before PAM account access#189
carlosmonastyrski wants to merge 4 commits intomainfrom
feature/PAM-184

Conversation

@carlosmonastyrski
Copy link
Copy Markdown
Contributor

Description 📣

New PAM access reason field introduced on Infisical/infisical#6096.

Type ✨

  • Bug fix
  • New feature
  • Improvement
  • Breaking change
  • Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

@linear
Copy link
Copy Markdown

linear Bot commented Apr 20, 2026

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d72335b1c1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread packages/pam/local/base-proxy.go Outdated
Comment thread packages/pam/local/base-proxy.go
Comment thread packages/pam/local/base-proxy.go
Comment thread packages/cmd/pam.go
Comment thread packages/cmd/pam.go Outdated
Comment thread packages/api/model.go
Comment thread packages/api/model.go
Comment thread packages/api/model.go

pamResponse, err := CallPAMAccessWithMFA(httpClient, pamRequest)
interactive := options.ExecCommand == ""
pamResponse, err := CallPAMAccessWithMFA(httpClient, pamRequest, interactive)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Right now, for SSH, we are not asking for the optional reason, both on the CLI and in the web. I think we should only disable this optional prompt for SSH EXEC and not for SSH ACCESS.

This will make SSH consistent with other resource types.

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