[GH-ISSUE #993] FEATURE REQUEST: #522

New issue

Closed

opened 2026-03-02 12:42:55 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 12:42:55 +03:00

Owner

Originally created by @servant42 on GitHub (Jun 25, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/993

Is your feature request related to a problem? Please describe.
When deploying CIPP for the first time, the time investment and complexity to create SAM tokens is high, but the code to do so programmatically exists in the SAM Wizard already.

Describe the solution you'd like
I suggest changing the installation flow to wait until after installation to ask for the SAM tokens, and walk the user through the SAM Wizard for the first time (if the tokens don't exist already, for example, which could also trigger if the user deletes the tokens as a way to prompt their regeneration, for admin users at least), with an alternate set of manual directions if it fails or needs troubleshooting, making the experience of first time and updated tokens similar and streamlining the installation.

Describe alternatives you've considered
Alternately, a checkbox to bypass the tokens and allow adding after install, if allowing them to be added up front is still desirable as an option. Or, add the wizard into the deployment process, but I suspect that dropping into the SAM wizard if the tokens don't exist on first login but after install is a simpler workflow.

Additional context
I admit it's been about a month or so since my last installation and it's possible I'm out of the loop and this is already addressed.

Originally created by @servant42 on GitHub (Jun 25, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/993 **Is your feature request related to a problem? Please describe.** When deploying CIPP for the first time, the time investment and complexity to create SAM tokens is high, but the code to do so programmatically exists in the SAM Wizard already. **Describe the solution you'd like** I suggest changing the installation flow to wait until after installation to ask for the SAM tokens, and walk the user through the SAM Wizard for the first time (if the tokens don't exist already, for example, which could also trigger if the user deletes the tokens as a way to prompt their regeneration, for admin users at least), with an alternate set of manual directions if it fails or needs troubleshooting, making the experience of first time and updated tokens similar and streamlining the installation. **Describe alternatives you've considered** Alternately, a checkbox to bypass the tokens and allow adding after install, if allowing them to be added up front is still desirable as an option. Or, add the wizard into the deployment process, but I suspect that dropping into the SAM wizard if the tokens don't exist on first login but after install is a simpler workflow. **Additional context** I admit it's been about a month or so since my last installation and it's possible I'm out of the loop and this is already addressed.

kerem

2026-03-02 12:42:55 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 12:42:56 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jun 26, 2022):

already in dev.

@KelvinTegelaar commented on GitHub (Jun 26, 2022): already in dev.

kerem referenced this issue

2026-03-02 13:55:51 +03:00

[PR #522] [MERGED] Fixes #517 - Access check table. #2875

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#522

No description provided.

Rows
Columns